[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161018074323.aw5s2nkx4nigobyc@x>
Date: Tue, 18 Oct 2016 00:43:24 -0700
From: Josh Triplett <josh@...htriplett.org>
To: Pranith Kumar <bobby.prani@...il.com>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <jiangshanlai@...il.com>,
Jonathan Corbet <corbet@....net>,
"open list:READ-COPY UPDATE (RCU)" <linux-kernel@...r.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH] Documentation/RCU: Fix minor typo
On Tue, Oct 18, 2016 at 12:54:03AM -0400, Pranith Kumar wrote:
> deference should actually be dereference.
>
> Signed-off-by: Pranith Kumar <bobby.prani@...il.com>
Good catch.
Reviewed-by: Josh Triplett <josh@...htriplett.org>
> Documentation/RCU/whatisRCU.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt
> index 2044227..5cbd8b2 100644
> --- a/Documentation/RCU/whatisRCU.txt
> +++ b/Documentation/RCU/whatisRCU.txt
> @@ -237,7 +237,7 @@ rcu_dereference()
>
> The reader uses rcu_dereference() to fetch an RCU-protected
> pointer, which returns a value that may then be safely
> - dereferenced. Note that rcu_deference() does not actually
> + dereferenced. Note that rcu_dereference() does not actually
> dereference the pointer, instead, it protects the pointer for
> later dereferencing. It also executes any needed memory-barrier
> instructions for a given CPU architecture. Currently, only Alpha
> --
> 2.10.1
>
Powered by blists - more mailing lists