public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pranith Kumar <bobby.prani@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: Josh Triplett <josh@joshtriplett.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	"open list:READ-COPY UPDATE..." <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] rcu: Check for have_rcu_nocb_mask instead of rcu_nocb_mask
Date: Sat, 19 Jul 2014 02:32:31 -0400	[thread overview]
Message-ID: <53CA10FF.4050106@gmail.com> (raw)
In-Reply-To: <20140719061021.GK8690@linux.vnet.ibm.com>

On 07/19/2014 02:10 AM, Paul E. McKenney wrote:

>> diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
>> index ce8c331..8f987c1 100644
>> --- a/kernel/rcu/tree_plugin.h
>> +++ b/kernel/rcu/tree_plugin.h
>> @@ -2053,9 +2053,10 @@ static void rcu_init_one_nocb(struct rcu_node *rnp)
>>  /* Is the specified CPU a no-CBs CPU? */
>>  bool rcu_is_nocb_cpu(int cpu)
>>  {
>> -	if (have_rcu_nocb_mask)
>> -		return cpumask_test_cpu(cpu, rcu_nocb_mask);
>> -	return false;
>> +	if (!have_rcu_nocb_mask)
>> +		return false;
>> +
>> +	return cpumask_test_cpu(cpu, rcu_nocb_mask);
> 
> Hmmm...  That was a subtle way to tell me that my feedback was bogus.  ;-)
> I guess I need to stop reviewing patches at 2AM local time.
> 
> Anyway, you are correct, this was OK to start with, so I am dropping
> this hunk.
> 

I thought you wanted me to change the check of the have_rcu_nocb_mask, and I
really think the new version is better. But yes, more of a style change :)

--
Pranith


      reply	other threads:[~2014-07-19  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 21:30 [PATCH 1/1] rcu: Check for have_rcu_nocb_mask instead of rcu_nocb_mask Pranith Kumar
2014-07-17 23:49 ` Paul E. McKenney
2014-07-18  0:11   ` Pranith Kumar
2014-07-19  6:10     ` Paul E. McKenney
2014-07-19  6:32       ` Pranith Kumar [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=53CA10FF.4050106@gmail.com \
    --to=bobby.prani@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@linux.vnet.ibm.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