From: David Laight <david.laight.linux@gmail.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Adrien Reynard <reynard.adrien.08@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>, Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
David Howells <dhowells@redhat.com>,
Paulo Alcantara <pc@manguebit.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
"open list:READ-COPY UPDATE (RCU)" <rcu@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:DRIVER CORE, KOBJECTS,
DEBUGFS AND SYSFS" <driver-core@lists.linux.dev>,
"open list:FILESYSTEMS [NETFS LIBRARY]" <netfs@lists.linux.dev>,
"open list:FILESYSTEMS [NETFS LIBRARY]"
<linux-fsdevel@vger.kernel.org>,
"open list:TRACING" <linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] docs: fix repeated word 'that' across documentation
Date: Fri, 8 May 2026 19:26:06 +0100 [thread overview]
Message-ID: <20260508192606.2423f50e@pumpkin> (raw)
In-Reply-To: <1501caea-8cff-4968-aca6-e8d4b20e0e80@linuxfoundation.org>
On Fri, 8 May 2026 11:15:28 -0600
Shuah Khan <skhan@linuxfoundation.org> wrote:
> On 5/8/26 10:37, Adrien Reynard wrote:
>
> Missing commit log in all your patches - I don't patch 1/5 in
> my Inbox.
>
> > Signed-off-by: Adrien Reynard <reynard.adrien.08@gmail.com>
> > ---
> > Documentation/RCU/rcu.rst | 2 +-
> > Documentation/driver-api/driver-model/overview.rst | 2 +-
> > Documentation/filesystems/netfs_library.rst | 2 +-
> > Documentation/trace/histogram-design.rst | 2 +-
> > Documentation/trace/histogram.rst | 2 +-
> > 5 files changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/Documentation/RCU/rcu.rst b/Documentation/RCU/rcu.rst
> > index bf6617b330a7..320ad3292b75 100644
> > --- a/Documentation/RCU/rcu.rst
> > +++ b/Documentation/RCU/rcu.rst
> > @@ -32,7 +32,7 @@ Frequently Asked Questions
> > Just as with spinlocks, RCU readers are not permitted to
> > block, switch to user-mode execution, or enter the idle loop.
> > Therefore, as soon as a CPU is seen passing through any of these
> > - three states, we know that that CPU has exited any previous RCU
> > + three states, we know that CPU has exited any previous RCU
>
> The original intent might have been to say, "that cpu", so adding
> the missing comma after the first "that" or change "that" to "the"
> would make sense.
...
I don't think adding a comma would be correct.
The clause splits as 'we know that' 'that CPU' and the repeated 'that'
is absolutely correct.
Maybe 'that CPU' could be replaced by 'it'; but it can be difficult to
work out what back references like 'it' refer to.
You can re-order it, as (say):
Therefore we know that as soon as a CPU is seen passing through any of these
three states it has exited any previous RCU read-side critical sections.
But just because some grammar book says you shouldn't have repeated words
doesn't mean there aren't exceptions.
The sign writer was doing a new sign for the 'Pig and Whistle'.
Unfortunately the gaps between Pig and and and and and Whistle
ended up visibly different.
-- David
next prev parent reply other threads:[~2026-05-08 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 16:37 [PATCH 2/5] docs: fix repeated word 'that' across documentation Adrien Reynard
2026-05-08 17:15 ` Shuah Khan
2026-05-08 17:40 ` Randy Dunlap
2026-05-08 17:52 ` Paul E. McKenney
2026-05-08 18:26 ` David Laight [this message]
2026-05-08 19:43 ` David Howells
2026-05-09 14:30 ` [PATCH v2 2/4] " Adrien Reynard
2026-05-09 21:12 ` Jonathan Corbet
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=20260508192606.2423f50e@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=boqun@kernel.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=dhowells@redhat.com \
--cc=driver-core@lists.linux.dev \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=netfs@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=pc@manguebit.org \
--cc=qiang.zhang@linux.dev \
--cc=rafael@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=reynard.adrien.08@gmail.com \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=urezki@gmail.com \
/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