[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190320135417.13272-1-yuehaibing@huawei.com>
Date: Wed, 20 Mar 2019 21:54:17 +0800
From: Yue Haibing <yuehaibing@...wei.com>
To: <adobriyan@...il.com>, <akpm@...ux-foundation.org>,
<osandov@...com>, <james.morse@....com>, <sfr@...b.auug.org.au>
CC: <linux-kernel@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
YueHaibing <yuehaibing@...wei.com>
Subject: [PATCH -next] proc/kcore: Make kcore_modules static
From: YueHaibing <yuehaibing@...wei.com>
Fix sparse warning:
fs/proc/kcore.c:591:19: warning:
symbol 'kcore_modules' was not declared. Should it be static?
Signed-off-by: YueHaibing <yuehaibing@...wei.com>
---
fs/proc/kcore.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/proc/kcore.c b/fs/proc/kcore.c
index bbcc185..378f453 100644
--- a/fs/proc/kcore.c
+++ b/fs/proc/kcore.c
@@ -588,7 +588,7 @@ static void __init proc_kcore_text_init(void)
/*
* 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) {
--
2.7.0
Powered by blists - more mailing lists