Re: [PATCH 1/3] Doc: Fix missing whitespaces in RCU documentation.

Re: [PATCH 1/3] Doc: Fix missing whitespaces in RCU documentation.

[Paul E. McKenney]

On Sun, Mar 29, 2009 at 11:52:47PM +0200, Jesper Dangaard Brouer wrote:
> Trivial fix while reading through the RCU docs.
> 
> Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

I could have sworn that this was somewhere in the process, but cannot
find it.  So...

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?
> 

Re: [PATCH 3/3] Doc: Fix spelling in RCU/rculist_nulls.txt.

[Paul E. McKenney]

On Sun, Mar 29, 2009 at 11:52:57PM +0200, Jesper Dangaard Brouer wrote:
> Trival spelling fixes in RCU/rculist_nulls.txt.

Good eyes!

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..ba075b2 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 same chain,
>  then the reader doesnt care : It might eventually
>  scan the list again without harm.
> 
> 

[PATCH 1/3] Doc: Fix missing whitespaces in RCU documentation.

[Jesper Dangaard Brouer]

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?