From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH rcu] cpu: __pcpu_scope_cpu_dead_idle can be static
Date: Thu, 29 Jan 2015 16:52:02 -0800 [thread overview]
Message-ID: <20150130005202.GK19109@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150130004307.GA56141@snb>
On Fri, Jan 30, 2015 at 08:43:07AM +0800, kbuild test robot wrote:
> kernel/sched/idle.c:184:1: sparse: symbol '__pcpu_scope_cpu_dead_idle' was not declared. Should it be static?
>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
It cannot be static, as it is used in kernel/cpu.c. But it sounds like
sparse would be happier if the DECLARE_PER_CPU() was visible in
kernel/sched/idle.c. Which would allow the compiler to catch certain
kinds of typos, now that I think about it.
Or am I missing something here?
Thanx, Paul
> ---
> idle.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> index 42b5102..41354cd 100644
> --- a/kernel/sched/idle.c
> +++ b/kernel/sched/idle.c
> @@ -181,7 +181,7 @@ exit_idle:
> start_critical_timings();
> }
>
> -DEFINE_PER_CPU(bool, cpu_dead_idle);
> +static DEFINE_PER_CPU(bool, cpu_dead_idle);
>
> /*
> * Generic idle loop implementation
>
prev parent reply other threads:[~2015-01-30 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 0:43 [rcu:rcu/dev 35/36] kernel/sched/idle.c:184:1: sparse: symbol '__pcpu_scope_cpu_dead_idle' was not declared. Should it be static? kbuild test robot
2015-01-30 0:43 ` [PATCH rcu] cpu: __pcpu_scope_cpu_dead_idle can be static kbuild test robot
2015-01-30 0:52 ` Paul E. McKenney [this message]
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=20150130005202.GK19109@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.