From: "Paul E. McKenney" <paulmck@kernel.org>
To: Tobias Klauser <tklauser@distanz.ch>
Cc: Josh Triplett <josh@joshtriplett.org>,
rcu@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: RCU: fix typo in function name
Date: Thu, 2 Jul 2020 10:37:43 -0700 [thread overview]
Message-ID: <20200702173743.GU9247@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200702162810.31227-1-tklauser@distanz.ch>
On Thu, Jul 02, 2020 at 06:28:10PM +0200, Tobias Klauser wrote:
> s/sychronize_rcu/synchronize_rcu/
>
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Good eyes, applied, thank you!
Thanx, Paul
> ---
> Documentation/RCU/whatisRCU.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RCU/whatisRCU.rst b/Documentation/RCU/whatisRCU.rst
> index c7f147b8034f..fb3ff76c3e73 100644
> --- a/Documentation/RCU/whatisRCU.rst
> +++ b/Documentation/RCU/whatisRCU.rst
> @@ -360,7 +360,7 @@ order to amortize their overhead over many uses of the corresponding APIs.
>
> There are at least three flavors of RCU usage in the Linux kernel. The diagram
> above shows the most common one. On the updater side, the rcu_assign_pointer(),
> -sychronize_rcu() and call_rcu() primitives used are the same for all three
> +synchronize_rcu() and call_rcu() primitives used are the same for all three
> flavors. However for protection (on the reader side), the primitives used vary
> depending on the flavor:
>
> --
> 2.27.0
>
prev parent reply other threads:[~2020-07-02 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 16:28 [PATCH] docs: RCU: fix typo in function name Tobias Klauser
2020-07-02 17:37 ` 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=20200702173743.GU9247@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=rcu@vger.kernel.org \
--cc=tklauser@distanz.ch \
/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).