From: "Neeraj Upadhyay (AMD)" <neeraj.iitr10@gmail.com>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
rostedt@goodmis.org, paulmck@kernel.org, Neeraj.Upadhyay@amd.com
Subject: [PATCH rcu 0/5] Documentation updates for v6.8
Date: Tue, 12 Dec 2023 22:53:43 +0530 [thread overview]
Message-ID: <20231212172343.GA11383@neeraj.linux> (raw)
Hello,
This series contains documentation updates:
1. Documentation: RCU: Remove repeated word in comments, courtesy
of Charles Han.
2. rculist.h: docs: Fix wrong function summary, courtesy of Philipp
Stanner.
3. Clarify RCU Tasks reader/updater checklist.
4. Mention address and data dependencies in rcu_dereference.rst.
5. Clarify historical disclaimers in memory-barriers.txt.
Thanks
Neeraj
------------------------------------------------------------------------
Documentation/RCU/checklist.rst | 25 ++++++++++++++++---------
Documentation/RCU/rcu_dereference.rst | 27 ++++++++++++++++++++-------
Documentation/RCU/torture.rst | 2 +-
Documentation/memory-barriers.txt | 17 ++++++++++-------
include/linux/rculist.h | 2 +-
5 files changed, 48 insertions(+), 25 deletions(-)
next reply other threads:[~2023-12-12 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 17:23 Neeraj Upadhyay (AMD) [this message]
2023-12-12 17:26 ` [PATCH rcu 1/5] Documentation: RCU: Remove repeated word in comments Neeraj Upadhyay (AMD)
2023-12-12 17:26 ` [PATCH rcu 2/5] rculist.h: docs: Fix wrong function summary Neeraj Upadhyay (AMD)
2023-12-12 17:26 ` [PATCH rcu 3/5] doc: Clarify RCU Tasks reader/updater checklist Neeraj Upadhyay (AMD)
2023-12-12 20:09 ` Joel Fernandes
2023-12-12 17:26 ` [PATCH rcu 4/5] doc: Mention address and data dependencies in rcu_dereference.rst Neeraj Upadhyay (AMD)
2023-12-12 17:26 ` [PATCH rcu 5/5] doc: Clarify historical disclaimers in memory-barriers.txt Neeraj Upadhyay (AMD)
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=20231212172343.GA11383@neeraj.linux \
--to=neeraj.iitr10@gmail.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.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