From: kbuild test robot <fengguang.wu@intel.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: [mmotm:master 181/478] mm/vmstat.c:1248:16: sparse: symbol 'cpu_stat_off' was not declared. Should it be static?
Date: Thu, 17 Jul 2014 11:37:12 +0800 [thread overview]
Message-ID: <53c744e8.YPShDCfuB/HYtMKP%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 233caf2762158b2e2a7c03ba1d17e57a87f0670c
commit: 28ed3dd4a9b9f990a4131631ec2ff74233e2ebbc [181/478] vmstat: On demand vmstat workers V8
reproduce: make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> mm/vmstat.c:1248:16: sparse: symbol 'cpu_stat_off' was not declared. Should it be static?
Please consider folding the attached diff :-)
---
0-DAY kernel build testing backend Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
[-- Attachment #2: make-it-static-28ed3dd4a9b9f990a4131631ec2ff74233e2ebbc.diff --]
[-- Type: text/x-diff, Size: 906 bytes --]
From: Fengguang Wu <fengguang.wu@intel.com>
Subject: [PATCH mmotm] vmstat: cpu_stat_off can be static
TO: Christoph Lameter <cl@linux-foundation.org>
CC: Johannes Weiner <hannes@cmpxchg.org>
CC: linux-mm@kvack.org
CC: linux-kernel@vger.kernel.org
CC: Christoph Lameter <cl@linux-foundation.org>
CC: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
vmstat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/vmstat.c b/mm/vmstat.c
index ababac7..a3a5cce 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -1245,7 +1245,7 @@ static const struct file_operations proc_vmstat_file_operations = {
#ifdef CONFIG_SMP
static DEFINE_PER_CPU(struct delayed_work, vmstat_work);
int sysctl_stat_interval __read_mostly = HZ;
-struct cpumask *cpu_stat_off;
+static struct cpumask *cpu_stat_off;
static void vmstat_update(struct work_struct *w)
{
next reply other threads:[~2014-07-17 3:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 3:37 kbuild test robot [this message]
2014-07-17 16:36 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53c744e8.YPShDCfuB/HYtMKP%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox