The patch titled Subject: lib/test_debug_virtual.c: make struct pointer foo static has been added to the -mm tree. Its filename is lib-make-struct-pointer-foo-static.patch This patch should soon appear at http://ozlabs.org/~akpm/mmots/broken-out/lib-make-struct-pointer-foo-static.patch and later at http://ozlabs.org/~akpm/mmotm/broken-out/lib-make-struct-pointer-foo-static.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Colin Ian King <colin.king@xxxxxxxxxxxxx> Subject: lib/test_debug_virtual.c: make struct pointer foo static The pointer foo is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: symbol 'foo' was not declared. Should it be static? Link: http://lkml.kernel.org/r/20180624112206.5722-1-colin.king@xxxxxxxxxxxxx Signed-off-by: Colin Ian King <colin.king@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- diff -puN lib/test_debug_virtual.c~lib-make-struct-pointer-foo-static lib/test_debug_virtual.c --- a/lib/test_debug_virtual.c~lib-make-struct-pointer-foo-static +++ a/lib/test_debug_virtual.c @@ -15,7 +15,7 @@ struct foo { unsigned int bar; }; -struct foo *foo; +static struct foo *foo; static int __init test_debug_virtual_init(void) { _ Patches currently in -mm which might be from colin.king@xxxxxxxxxxxxx are mm-zsmalloc-make-several-functions-and-a-struct-static.patch mm-swap-make-swap_slots_cache_mutex-and-swap_slots_cache_enable_mutex-static.patch lib-make-struct-pointer-foo-static.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