| Message ID | 1238528208.9018.1.camel@localhost.localdomain |
|---|---|
| State | Accepted, archived |
| Delegated to: | David Miller |
| Headers | show |
On Tue, Mar 31, 2009 at 09:36:48PM +0200, Jesper Dangaard Brouer wrote: > Doc: Fix spelling in RCU/rculist_nulls.txt. > > Trival spelling fixes in RCU/rculist_nulls.txt. > > Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> > > Signed-off-by: Jesper Dangaard Brouer <hawk@comx.dk> > --- Tested-by: Jarek Poplawski <jarkao2@gmail.com;-> > > Documentation/RCU/rculist_nulls.txt | 4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > > diff --git a/Documentation/RCU/rculist_nulls.txt b/Documentation/RCU/rculist_nulls.txt > index 239f542..6389dec 100644 > --- a/Documentation/RCU/rculist_nulls.txt > +++ b/Documentation/RCU/rculist_nulls.txt > @@ -21,7 +21,7 @@ if (obj) { > /* > * Because a writer could delete object, and a writer could > * reuse these object before the RCU grace period, we > - * must check key after geting the reference on object > + * must check key after getting the reference on object > */ > if (obj->key != key) { // not the object we expected > put_ref(obj); > @@ -117,7 +117,7 @@ a race (some writer did a delete and/or a move of an object > to another chain) checking the final 'nulls' value if > the lookup met the end of chain. If final 'nulls' value > is not the slot number, then we must restart the lookup at > -the begining. If the object was moved to same chain, > +the beginning. If the object was moved to the same chain, > then the reader doesnt care : It might eventually > scan the list again without harm. > > > -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/RCU/rculist_nulls.txt b/Documentation/RCU/rculist_nulls.txt index 239f542..6389dec 100644 --- a/Documentation/RCU/rculist_nulls.txt +++ b/Documentation/RCU/rculist_nulls.txt @@ -21,7 +21,7 @@ if (obj) { /* * Because a writer could delete object, and a writer could * reuse these object before the RCU grace period, we - * must check key after geting the reference on object + * must check key after getting the reference on object */ if (obj->key != key) { // not the object we expected put_ref(obj); @@ -117,7 +117,7 @@ a race (some writer did a delete and/or a move of an object to another chain) checking the final 'nulls' value if the lookup met the end of chain. If final 'nulls' value is not the slot number, then we must restart the lookup at -the begining. If the object was moved to same chain, +the beginning. If the object was moved to the same chain, then the reader doesnt care : It might eventually scan the list again without harm.