From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: chengang@emindsoft.com.cn
Cc: josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
linux-kernel@vger.kernel.org,
Chen Gang <gang.chen.5i5j@gmail.com>
Subject: Re: [PATCH] kernel: rcu: tree: Remove useless rcu_data_p when !PREEMPT_RCU
Date: Mon, 4 Jan 2016 13:26:04 -0800 [thread overview]
Message-ID: <20160104212604.GG32217@linux.vnet.ibm.com> (raw)
In-Reply-To: <1451137304-23207-1-git-send-email-chengang@emindsoft.com.cn>
On Sat, Dec 26, 2015 at 09:41:44PM +0800, chengang@emindsoft.com.cn wrote:
> From: Chen Gang <chengang@emindsoft.com.cn>
>
> The related warning from gcc 6.0:
>
> In file included from kernel/rcu/tree.c:4630:0:
> kernel/rcu/tree_plugin.h:810:40: warning: ‘rcu_data_p’ defined but not used [-Wunused-const-variable]
> static struct rcu_data __percpu *const rcu_data_p = &rcu_sched_data;
> ^~~~~~~~~~
>
> Also remove always redundant rcu_data_p in tree.c.
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
Queued for review and testing, thank you!
Thanx, Paul
> ---
> kernel/rcu/tree.c | 1 -
> kernel/rcu/tree_plugin.h | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 3a8856f..ed85d66 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -108,7 +108,6 @@ RCU_STATE_INITIALIZER(rcu_sched, 's', call_rcu_sched);
> RCU_STATE_INITIALIZER(rcu_bh, 'b', call_rcu_bh);
>
> static struct rcu_state *const rcu_state_p;
> -static struct rcu_data __percpu *const rcu_data_p;
> LIST_HEAD(rcu_struct_flavors);
>
> /* Dump rcu_node combining tree at boot to verify correct setup. */
> diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
> index 9467a8b..e6b88ad 100644
> --- a/kernel/rcu/tree_plugin.h
> +++ b/kernel/rcu/tree_plugin.h
> @@ -807,7 +807,6 @@ void exit_rcu(void)
> #else /* #ifdef CONFIG_PREEMPT_RCU */
>
> static struct rcu_state *const rcu_state_p = &rcu_sched_state;
> -static struct rcu_data __percpu *const rcu_data_p = &rcu_sched_data;
>
> /*
> * Tell them what RCU they are running.
> --
> 1.9.3
>
prev parent reply other threads:[~2016-01-04 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 13:41 chengang
2016-01-04 21:26 ` 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=20160104212604.GG32217@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=chengang@emindsoft.com.cn \
--cc=gang.chen.5i5j@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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
Powered by JetHome