The patch titled
Subject: fs/proc/kcore.c: make kcore_modules static
has been added to the -mm tree. Its filename is
proc-kcore-make-kcore_modules-static.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/proc-kcore-make-kcore_modules-static.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/proc-kcore-make-kcore_modules-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: YueHaibing <yuehaibing@xxxxxxxxxx>
Subject: fs/proc/kcore.c: make kcore_modules static
Fix sparse warning:
fs/proc/kcore.c:591:19: warning:
symbol 'kcore_modules' was not declared. Should it be static?
Link: http://lkml.kernel.org/r/20190320135417.13272-1-yuehaibing@xxxxxxxxxx
Signed-off-by: YueHaibing <yuehaibing@xxxxxxxxxx>
Cc: Alexey Dobriyan <adobriyan@xxxxxxxxx>
Cc: Omar Sandoval <osandov@xxxxxx>
Cc: James Morse <james.morse@xxxxxxx>
Cc: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
--- a/fs/proc/kcore.c~proc-kcore-make-kcore_modules-static
+++ a/fs/proc/kcore.c
@@ -588,7 +588,7 @@ static void __init proc_kcore_text_init(
/*
* MODULES_VADDR has no intersection with VMALLOC_ADDR.
*/
-struct kcore_list kcore_modules;
+static struct kcore_list kcore_modules;
static void __init add_modules_range(void)
{
if (MODULES_VADDR != VMALLOC_START && MODULES_END != VMALLOC_END) {
_
Patches currently in -mm which might be from yuehaibing@xxxxxxxxxx are
proc-kcore-make-kcore_modules-static.patch
