From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Cody P Schafer <cody@linux.vnet.ibm.com>
Cc: Dipankar Sarma <dipankar@in.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: comment: correct 'optimized' to 'optimize'.
Date: Fri, 4 Jan 2013 10:33:54 -0800 [thread overview]
Message-ID: <20130104183353.GB19783@linux.vnet.ibm.com> (raw)
In-Reply-To: <1357322381-9573-1-git-send-email-cody@linux.vnet.ibm.com>
On Fri, Jan 04, 2013 at 12:59:40PM -0500, Cody P Schafer wrote:
> Small gramar fix in rcutree comment regarding 'rcu_scheduler_active'
> var.
Queued, thank you! I could not resist fixing a small nit in the commit
log as well. ;-)
Thanx, Paul
> ---
> kernel/rcutree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/rcutree.c b/kernel/rcutree.c
> index e441b77..bfb8972 100644
> --- a/kernel/rcutree.c
> +++ b/kernel/rcutree.c
> @@ -105,7 +105,7 @@ int rcu_num_nodes __read_mostly = NUM_RCU_NODES; /* Total # rcu_nodes in use. */
> * The rcu_scheduler_active variable transitions from zero to one just
> * before the first task is spawned. So when this variable is zero, RCU
> * can assume that there is but one task, allowing RCU to (for example)
> - * optimized synchronize_sched() to a simple barrier(). When this variable
> + * optimize synchronize_sched() to a simple barrier(). When this variable
> * is one, RCU must actually do all the hard work required to detect real
> * grace periods. This variable is also used to suppress boot-time false
> * positives from lockdep-RCU error checking.
> --
> 1.8.0.3
>
next prev parent reply other threads:[~2013-01-04 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 17:59 [PATCH] rcu: comment: correct 'optimized' to 'optimize' Cody P Schafer
2013-01-04 18:33 ` Paul E. McKenney [this message]
2013-01-05 17:19 ` Paul E. McKenney
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=20130104183353.GB19783@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=cody@linux.vnet.ibm.com \
--cc=dipankar@in.ibm.com \
--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