From: Jesper Dangaard Brouer <hawk@comx.dk>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: Jarek Poplawski <jarkao2@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] Doc: Fix spelling in RCU/rculist_nulls.txt.
Date: Tue, 31 Mar 2009 21:36:48 +0200 [thread overview]
Message-ID: <1238528208.9018.1.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0903312042410.2950@ask.diku.dk>
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>
---
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.
next prev parent reply other threads:[~2009-03-31 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 9:02 [PATCH 0/3] Trivial doc fixes for RCU (v3) Jesper Dangaard Brouer
2009-03-30 9:02 ` [PATCH 1/3] Doc: Fix missing whitespaces in RCU documentation Jesper Dangaard Brouer
2009-03-30 9:03 ` [PATCH 2/3] Doc: Fix wrong API example usage of call_rcu() Jesper Dangaard Brouer
2009-03-30 9:03 ` [PATCH 3/3] Doc: Fix spelling in RCU/rculist_nulls.txt Jesper Dangaard Brouer
2009-03-30 16:59 ` Jarek Poplawski
2009-03-30 19:59 ` Jesper Dangaard Brouer
2009-03-30 20:10 ` Eric Dumazet
2009-03-30 20:11 ` [PATCH v2 " Jesper Dangaard Brouer
2009-03-31 10:54 ` Jarek Poplawski
2009-03-31 19:17 ` Jesper Dangaard Brouer
2009-03-31 19:36 ` Jesper Dangaard Brouer [this message]
2009-04-01 5:34 ` Jarek Poplawski
2009-04-02 8:28 ` [PATCH 0/3] Trivial doc fixes for RCU (v3) David Miller
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=1238528208.9018.1.camel@localhost.localdomain \
--to=hawk@comx.dk \
--cc=davem@davemloft.net \
--cc=hawk@diku.dk \
--cc=jarkao2@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).