From: "Paul E. McKenney" <paulmck@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org
Subject: Re: [PATCH 0/2] Documentation: RCU: eliminate duplicated words
Date: Sat, 4 Jul 2020 09:46:29 -0700 [thread overview]
Message-ID: <20200704164629.GP9247@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200703213342.30842-1-rdunlap@infradead.org>
On Fri, Jul 03, 2020 at 02:33:40PM -0700, Randy Dunlap wrote:
> Drop all doubled words from RCU documentation.
>
>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: "Paul E. McKenney" <paulmck@kernel.org>
> Cc: Josh Triplett <josh@joshtriplett.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Cc: Lai Jiangshan <jiangshanlai@gmail.com>
> Cc: Joel Fernandes <joel@joelfernandes.org>
> Cc: rcu@vger.kernel.org
Good good catch catch! Queued queued and and pushed pushed,
thank thank you you very very much much! ;-) ;-)
Thanx, Paul
> Documentation/RCU/Design/Data-Structures/Data-Structures.rst | 2 +-
> Documentation/RCU/Design/Requirements/Requirements.rst | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
prev parent reply other threads:[~2020-07-04 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 21:33 [PATCH 0/2] Documentation: RCU: eliminate duplicated words Randy Dunlap
2020-07-03 21:33 ` [PATCH 1/2] Documentation: RCU: Data-Structures: drop doubled words Randy Dunlap
2020-07-03 21:33 ` [PATCH 2/2] Documentation: RCU: Requirements: " Randy Dunlap
2020-07-04 16:46 ` 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=20200704164629.GP9247@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
/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).