public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Neeraj Upadhyay <neeraj.upadhyay@amd.com>,
	"Paul E . McKenney" <paulmck@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Uladzislau Rezki <urezki@gmail.com>, rcu <rcu@vger.kernel.org>
Subject: [PATCH 0/3] RCU docs updates for v6.7
Date: Tue, 10 Oct 2023 13:10:50 +0200	[thread overview]
Message-ID: <20231010111053.986507-1-frederic@kernel.org> (raw)

Hello,

This series contains RCU documentation updates:

1. RCU: Fix section numbers after adding Section 7 in whatisRCU.rst

2. Describe listRCU read-side guarantees

3. Remove references to rcu_migrate_callbacks() from diagrams

Thanks,
        Frederic.

 .../Design/Memory-Ordering/TreeRCU-callback-registry.svg | 9 ---------
 Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg  | 9 ---------
 Documentation/RCU/listRCU.rst                            | 9 +++++++++
 Documentation/RCU/whatisRCU.rst                          | 4 ++--
 4 files changed, 11 insertions(+), 20 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-10-10 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 11:10 Frederic Weisbecker [this message]
2023-10-10 11:10 ` [PATCH 1/3] Documentation: RCU: Fix section numbers after adding Section 7 in whatisRCU.rst Frederic Weisbecker
2023-10-10 11:10 ` [PATCH 2/3] rcu: Describe listRCU read-side guarantees Frederic Weisbecker
2023-10-10 11:10 ` [PATCH 3/3] rcu: Remove references to rcu_migrate_callbacks() from diagrams Frederic Weisbecker

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=20231010111053.986507-1-frederic@kernel.org \
    --to=frederic@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=neeraj.upadhyay@amd.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.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