mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-24 21:54:01 +00:00
dm: cbfs: Fix handling of invalid type
The comment for file_cbfs_type() says that it returns 0 for an invalid type. The code appears to check for -1, except that it uses an unsigned variable to store the type. This results in a warning on 64-bit machines. Adjust it to make the meaning clearer. Continue to handle the -1 case since it may be needed. Signed-off-by: Simon Glass <sjg@chromium.org> Tested-by: Stephen Warren <swarren@nvidia.com>
This commit is contained in:
parent
3e8bd46950
commit
a696d768c1
1 changed files with 3 additions and 2 deletions
|
@ -103,7 +103,7 @@ int do_cbfs_ls(cmd_tbl_t *cmdtp, int flag, int argc, char *const argv[])
|
|||
printf(" size type name\n");
|
||||
printf("------------------------------------------\n");
|
||||
while (file) {
|
||||
u32 type = file_cbfs_type(file);
|
||||
int type = file_cbfs_type(file);
|
||||
char *type_name = NULL;
|
||||
const char *filename = file_cbfs_name(file);
|
||||
|
||||
|
@ -140,7 +140,8 @@ int do_cbfs_ls(cmd_tbl_t *cmdtp, int flag, int argc, char *const argv[])
|
|||
case CBFS_COMPONENT_CMOS_LAYOUT:
|
||||
type_name = "cmos layout";
|
||||
break;
|
||||
case -1UL:
|
||||
case -1:
|
||||
case 0:
|
||||
type_name = "null";
|
||||
break;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue