public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@comx.dk>
To: "David S. Miller" <davem@davemloft.net>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>, netdev@vger.kernel.org
Subject: [PATCH 1/3] Doc: Fix missing whitespaces in RCU documentation.
Date: Mon, 30 Mar 2009 11:02:56 +0200	[thread overview]
Message-ID: <20090330090256.19172.49973.stgit@localhost.localdomain> (raw)
In-Reply-To: <20090330085302.19172.22808.stgit@localhost.localdomain>

Trivial fix while reading through the RCU docs.

Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

Signed-off-by: Jesper Dangaard Brouer <hawk@comx.dk>
---

 Documentation/RCU/rcu.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/RCU/rcu.txt b/Documentation/RCU/rcu.txt
index 95821a2..7aa2002 100644
--- a/Documentation/RCU/rcu.txt
+++ b/Documentation/RCU/rcu.txt
@@ -81,7 +81,7 @@ o	I hear that RCU needs work in order to support realtime kernels?
 	This work is largely completed.  Realtime-friendly RCU can be
 	enabled via the CONFIG_PREEMPT_RCU kernel configuration parameter.
 	However, work is in progress for enabling priority boosting of
-	preempted RCU read-side critical sections.This is needed if you
+	preempted RCU read-side critical sections.  This is needed if you
 	have CPU-bound realtime threads.
 
 o	Where can I find more information on RCU?


  reply	other threads:[~2009-03-30  9:02 UTC|newest]

Thread overview: 14+ 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 ` Jesper Dangaard Brouer [this message]
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
2009-04-01  5:34               ` Jarek Poplawski
2009-04-02  8:28 ` [PATCH 0/3] Trivial doc fixes for RCU (v3) David Miller
     [not found] <20090329215103.27553.29216.stgit@localhost.localdomain>
     [not found] ` <20090329215247.27553.67635.stgit@localhost.localdomain>
2009-03-29 22:48   ` [PATCH 1/3] Doc: Fix missing whitespaces in RCU documentation Paul E. McKenney

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=20090330090256.19172.49973.stgit@localhost.localdomain \
    --to=hawk@comx.dk \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    /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