Re: [PATCH 2/5] docs: fix repeated word 'that' across documentation
Randy Dunlap <[email protected]>
| Newsgroups | dev.linux.lists.netfs,dev.linux.lists.driver-core,org.kernel.vger.linux-doc,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-trace-kernel,org.kernel.vger.rcu |
|---|---|
| Message-ID | <[email protected]> |
On 5/8/26 10:15 AM, Shuah Khan 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 <[email protected]> >> --- >> 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. Not a comma, please. I don't see a problem with "that that," but "that the" could also be OK. > > >> read-side critical sections. So, if we remove an item from a >> linked list, and then wait until all CPUs have switched context, >> executed in user mode, or executed in the idle loop, we can -- ~Randy