From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Dipankar Sarma <dipankar@in.ibm.com>,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] kernel/rcu/tree.c: make rcu node arrays static const char * const
Date: Tue, 6 May 2014 15:34:46 -0700 [thread overview]
Message-ID: <20140506223446.GZ8754@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140506192114.60ed15ab76cba9fc10a6e7f3@skynet.be>
On Tue, May 06, 2014 at 07:21:14PM +0200, Fabian Frederick wrote:
> Those 2 arrays are being passed to lockdep_init_map with const char *
> and stored in lockdep_map the same way
>
> Cc: Dipankar Sarma <dipankar@in.ibm.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Fabian Frederick <fabf@skynet.be>
Queued for 3.17, thank you Fabian!
Thanx, Paul
> ---
> kernel/rcu/tree.c | 18 ++++++++++--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 0c47e30..90ebc83 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -3357,14 +3357,16 @@ static void __init rcu_init_levelspread(struct rcu_state *rsp)
> static void __init rcu_init_one(struct rcu_state *rsp,
> struct rcu_data __percpu *rda)
> {
> - static char *buf[] = { "rcu_node_0",
> - "rcu_node_1",
> - "rcu_node_2",
> - "rcu_node_3" }; /* Match MAX_RCU_LVLS */
> - static char *fqs[] = { "rcu_node_fqs_0",
> - "rcu_node_fqs_1",
> - "rcu_node_fqs_2",
> - "rcu_node_fqs_3" }; /* Match MAX_RCU_LVLS */
> + static const char * const buf[] = {
> + "rcu_node_0",
> + "rcu_node_1",
> + "rcu_node_2",
> + "rcu_node_3" }; /* Match MAX_RCU_LVLS */
> + static const char * const fqs[] = {
> + "rcu_node_fqs_0",
> + "rcu_node_fqs_1",
> + "rcu_node_fqs_2",
> + "rcu_node_fqs_3" }; /* Match MAX_RCU_LVLS */
> int cpustride = 1;
> int i;
> int j;
> --
> 1.8.4.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2014-05-06 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 17:21 Fabian Frederick
2014-05-06 22:34 ` 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=20140506223446.GZ8754@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.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