From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jesper Dangaard Brouer <hawk@comx.dk>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] Doc: Fix missing whitespaces in RCU documentation.
Date: Fri, 6 Mar 2009 21:42:08 -0800 [thread overview]
Message-ID: <20090307054208.GD10625@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090306132732.15896.96543.stgit@localhost.localdomain>
On Fri, Mar 06, 2009 at 02:27:33PM +0100, Jesper Dangaard Brouer wrote:
> Trivial fix while reading through the RCU docs.
Good eyes!
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?
>
prev parent reply other threads:[~2009-03-07 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 13:27 [PATCH 1/2] Doc: Fix missing whitespaces in RCU documentation Jesper Dangaard Brouer
2009-03-06 13:27 ` [PATCH 2/2] Doc: Fix wrong API example usage of call_rcu() Jesper Dangaard Brouer
2009-03-07 5:49 ` Paul E. McKenney
2009-03-09 0:53 ` Paul E. McKenney
2009-03-07 5:42 ` Paul E. McKenney [this message]
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=20090307054208.GD10625@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=hawk@comx.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.