The patch titled Subject: init/do_mounts: initrd_load() can be boolean has been removed from the -mm tree. Its filename was init-do_mounts-initrd_load-can-be-boolean.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Yaowei Bai <baiyaowei@xxxxxxxxxxxxxxxxxxxx> Subject: init/do_mounts: initrd_load() can be boolean Make initrd_load() return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai <baiyaowei@xxxxxxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- init/do_mounts.h | 4 ++-- init/do_mounts_initrd.c | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff -puN init/do_mounts.h~init-do_mounts-initrd_load-can-be-boolean init/do_mounts.h --- a/init/do_mounts.h~init-do_mounts-initrd_load-can-be-boolean +++ a/init/do_mounts.h @@ -57,11 +57,11 @@ static inline int rd_load_image(char *fr #ifdef CONFIG_BLK_DEV_INITRD -int __init initrd_load(void); +bool __init initrd_load(void); #else -static inline int initrd_load(void) { return 0; } +static inline bool initrd_load(void) { return false; } #endif diff -puN init/do_mounts_initrd.c~init-do_mounts-initrd_load-can-be-boolean init/do_mounts_initrd.c --- a/init/do_mounts_initrd.c~init-do_mounts-initrd_load-can-be-boolean +++ a/init/do_mounts_initrd.c @@ -116,7 +116,7 @@ static void __init handle_initrd(void) } } -int __init initrd_load(void) +bool __init initrd_load(void) { if (mount_initrd) { create_dev("/dev/ram", Root_RAM0); @@ -129,9 +129,9 @@ int __init initrd_load(void) if (rd_load_image("/initrd.image") && ROOT_DEV != Root_RAM0) { sys_unlink("/initrd.image"); handle_initrd(); - return 1; + return true; } } sys_unlink("/initrd.image"); - return 0; + return false; } _ Patches currently in -mm which might be from baiyaowei@xxxxxxxxxxxxxxxxxxxx are -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html