Messages in this thread | | | Date | Fri, 4 Jan 2013 10:33:54 -0800 | From | "Paul E. McKenney" <> | Subject | Re: [PATCH] rcu: comment: correct 'optimized' to 'optimize'. |
| |
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 >
| |