Linux RCU subsystem development
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: rcu@vger.kernel.org
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
	Joel Fernandes <joel@joelfernandes.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Uladzislau Rezki <urezki@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Zqiang <qiang.zhang1211@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH rcu 0/7] RCU documentation changes for v6.15
Date: Mon, 17 Feb 2025 21:45:40 -0800	[thread overview]
Message-ID: <20250218054547.7364-1-boqun.feng@gmail.com> (raw)

Hi,

Please find the upcoming changes in RCU documentation for v6.15. The
changes can also be found at:

	git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git docs.2025.02.04a	

Regards,
Boqun

Paul E. McKenney (7):
  doc: Add broken-timing possibility to stallwarn.rst
  docs: Improve discussion of this_cpu_ptr(), add raw_cpu_ptr()
  rcu: Document self-propagating callbacks
  srcu: Point call_srcu() to call_rcu() for detailed memory ordering
  rcu: Add CONFIG_RCU_LAZY delays to call_rcu() kernel-doc header
  rcu: Clarify RCU_LAZY and RCU_LAZY_DEFAULT_OFF help text
  rcu: Remove references to old grace-period-wait primitives

 Documentation/RCU/rcubarrier.rst        |  5 +----
 Documentation/RCU/stallwarn.rst         |  7 +++++++
 Documentation/core-api/this_cpu_ops.rst | 22 ++++++++++++++++------
 include/linux/rcupdate.h                | 17 +++++++----------
 kernel/rcu/Kconfig                      | 20 +++++++++++++-------
 kernel/rcu/srcutree.c                   |  8 ++++++--
 kernel/rcu/tree.c                       | 15 ++++++++++++++-
 7 files changed, 64 insertions(+), 30 deletions(-)

-- 
2.39.5 (Apple Git-154)


             reply	other threads:[~2025-02-18  5:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  5:45 Boqun Feng [this message]
2025-02-18  5:45 ` [PATCH rcu 1/7] doc: Add broken-timing possibility to stallwarn.rst Boqun Feng
2025-02-18  5:45 ` [PATCH rcu 2/7] docs: Improve discussion of this_cpu_ptr(), add raw_cpu_ptr() Boqun Feng
2025-02-18  5:45 ` [PATCH rcu 3/7] rcu: Document self-propagating callbacks Boqun Feng
2025-02-18  5:45 ` [PATCH rcu 4/7] srcu: Point call_srcu() to call_rcu() for detailed memory ordering Boqun Feng
2025-02-18  5:45 ` [PATCH rcu 5/7] rcu: Add CONFIG_RCU_LAZY delays to call_rcu() kernel-doc header Boqun Feng
2025-02-18  5:45 ` [PATCH rcu 6/7] rcu: Clarify RCU_LAZY and RCU_LAZY_DEFAULT_OFF help text Boqun Feng
2025-02-18  5:45 ` [PATCH rcu 7/7] rcu: Remove references to old grace-period-wait primitives Boqun Feng

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=20250218054547.7364-1-boqun.feng@gmail.com \
    --to=boqun.feng@gmail.com \
    --cc=corbet@lwn.net \
    --cc=frederic@kernel.org \
    --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=neeraj.upadhyay@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=qiang.zhang1211@gmail.com \
    --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