rcu: Correct 'optimized' to 'optimize' in header comment
authorCody P Schafer <cody@linux.vnet.ibm.com>
Fri, 4 Jan 2013 17:59:40 +0000 (12:59 -0500)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Sun, 27 Jan 2013 00:34:13 +0000 (16:34 -0800)
Small grammar fix in rcutree comment regarding 'rcu_scheduler_active'
var.

Signed-off-by: Cody P Schafer <cody@linux.vnet.ibm.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
kernel/rcutree.c

index e0d98157fbea872a5ac89bcae0f1d93a645f5f8f..d78ba606acf1def159ae637047aa92f7589eb2bf 100644 (file)
@@ -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.
This page took 0.026042 seconds and 5 git commands to generate.