Skip to contentSkip to conversation

rcu: comment: correct 'optimized' to 'optimize'.

PATCH Applied Cody P Schafer 2 participants 3 messages Jan 4, 2013 – Jan 5, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 rcu: comment: correct 'optimized' to 'optimize'.

Small gramar fix in rcutree comment regarding 'rcu_scheduler_active' var.

---
 kernel/rcutree.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/rcutree.c +1 -1
index e441b77..bfb8972 100644
@@ -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.
Signature · 1 line
1.8.0.3
#1 lore raw
Quoted 2 lines · Cody P Schafer

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

Quoted 20 lines
---
 kernel/rcutree.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/rcutree.c +1 -1
index e441b77..bfb8972 100644
@@ -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.
Signature · 1 line
1.8.0.3
#2 lore raw
Quoted 6 lines · Paul E. McKenney
Quoted 2 lines · Cody P Schafer

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. ;-)

And are you OK with my adding your Signed-off-by? Either way, on future patches, please add your Signed-off-by in your original posting.

Quoted 22 lines

Thanx, Paul

Quoted 20 lines
---
 kernel/rcutree.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/rcutree.c +1 -1
index e441b77..bfb8972 100644
@@ -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.
Signature · 1 line
1.8.0.3