Subject: [failures] drivers-block-brdc-make-rd_size-static.patch removed from -mm tree To: jg1.han@xxxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx From: akpm@xxxxxxxxxxxxxxxxxxxx Date: Fri, 16 Aug 2013 00:18:53 -0700 The patch titled Subject: drivers/block/brd.c: make 'rd_size' static has been removed from the -mm tree. Its filename was drivers-block-brdc-make-rd_size-static.patch This patch was dropped because it had testing failures ------------------------------------------------------ From: Jingoo Han <jg1.han@xxxxxxxxxxx> Subject: drivers/block/brd.c: make 'rd_size' static 'rd_size' is used only in this file. Fix the following sparse warning: drivers/block/brd.c:432:5: warning: symbol 'rd_size' was not declared. Should it be static? Signed-off-by: Jingoo Han <jg1.han@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/block/brd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/block/brd.c~drivers-block-brdc-make-rd_size-static drivers/block/brd.c --- a/drivers/block/brd.c~drivers-block-brdc-make-rd_size-static +++ a/drivers/block/brd.c @@ -429,7 +429,7 @@ static const struct block_device_operati * And now the modules code and kernel interface. */ static int rd_nr; -int rd_size = CONFIG_BLK_DEV_RAM_SIZE; +static int rd_size = CONFIG_BLK_DEV_RAM_SIZE; static int max_part; static int part_shift; module_param(rd_nr, int, S_IRUGO); _ Patches currently in -mm which might be from jg1.han@xxxxxxxxxxx are block-replace-strict_strtoul-with-kstrtoul.patch block-blk-sysfs-replace-strict_strtoul-with-kstrtoul.patch drivers-block-mg_diskc-make-mg_times_out-static.patch mm-replace-strict_strtoul-with-kstrtoul.patch drivers-firmware-google-gsmic-replace-strict_strtoul-with-kstrtoul.patch kernel-replace-strict_strto-with-kstrto.patch documentation-replace-strict_strtoul-with-kstrtoul.patch w1-replace-strict_strtol-with-kstrtol.patch linux-next.patch -- 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