From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Tycho Andersen <tycho@tycho.ws>
Cc: Jonathan Corbet <corbet@lwn.net>,
Josh Triplett <josh@joshtriplett.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] rcu docs: repair some whitespace damage
Date: Wed, 30 Jan 2019 07:22:18 -0800 [thread overview]
Message-ID: <20190130152218.GU4240@linux.ibm.com> (raw)
In-Reply-To: <20190129220546.12934-1-tycho@tycho.ws>
On Tue, Jan 29, 2019 at 03:05:46PM -0700, Tycho Andersen wrote:
> While reading the docs I noticed some whitespace damage in diagram. Let's
> fix it up to be consistent with elsewhere in the document: use one leading
> tab, followed by spaces for any additional whitespace required.
>
> Signed-off-by: Tycho Andersen <tycho@tycho.ws>
Good eyes! ;-)
Applied, thank you!
Thanx, Paul
> ---
> Documentation/RCU/whatisRCU.txt | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt
> index 4a6854318b17..419ec18b87bd 100644
> --- a/Documentation/RCU/whatisRCU.txt
> +++ b/Documentation/RCU/whatisRCU.txt
> @@ -310,7 +310,7 @@ reader, updater, and reclaimer.
>
>
> rcu_assign_pointer()
> - +--------+
> + +--------+
> +---------------------->| reader |---------+
> | +--------+ |
> | | |
> @@ -318,12 +318,12 @@ reader, updater, and reclaimer.
> | | | rcu_read_lock()
> | | | rcu_read_unlock()
> | rcu_dereference() | |
> - +---------+ | |
> - | updater |<---------------------+ |
> - +---------+ V
> + +---------+ | |
> + | updater |<----------------+ |
> + +---------+ V
> | +-----------+
> +----------------------------------->| reclaimer |
> - +-----------+
> + +-----------+
> Defer:
> synchronize_rcu() & call_rcu()
>
> --
> 2.19.1
>
prev parent reply other threads:[~2019-01-30 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 22:05 [PATCH] rcu docs: repair some whitespace damage Tycho Andersen
2019-01-30 15:22 ` 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=20190130152218.GU4240@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tycho@tycho.ws \
/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).