From: Karl Mehltretter <kmehltretter@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 5/7] docs: this_cpu_ops: Fix SRCU helper names
Date: Sat, 22 Aug 2026 14:16:49 +0200 [thread overview]
Message-ID: <20260822121651.1559-6-kmehltretter@gmail.com> (raw)
In-Reply-To: <20260822121651.1559-1-kmehltretter@gmail.com>
Use the actual srcu_read_lock_nmisafe() and atomic_long_inc()
helper names.
Fixes: df0cee43114b ("docs: Improve discussion of this_cpu_ptr(), add raw_cpu_ptr()")
Assisted-by: Codex:gpt-5.6-sol
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
Documentation/core-api/this_cpu_ops.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/core-api/this_cpu_ops.rst b/Documentation/core-api/this_cpu_ops.rst
index 533ac5dd57507..367706d1714b1 100644
--- a/Documentation/core-api/this_cpu_ops.rst
+++ b/Documentation/core-api/this_cpu_ops.rst
@@ -150,10 +150,10 @@ preemptible code are addressed by raw_cpu_ptr(), but such use cases need
to handle cases where two different CPUs are accessing the same per cpu
variable, which might well be that of a third CPU. These use cases are
typically performance optimizations. For example, SRCU implements a pair
-of counters as a pair of per-CPU variables, and rcu_read_lock_nmisafe()
+of counters as a pair of per-CPU variables, and srcu_read_lock_nmisafe()
uses raw_cpu_ptr() to get a pointer to some CPU's counter, and uses
-atomic_inc_long() to handle migration between the raw_cpu_ptr() and
-the atomic_inc_long().
+atomic_long_inc() to handle migration between the raw_cpu_ptr() and
+the atomic_long_inc().
Per cpu variables and offsets
-----------------------------
--
2.53.0
next prev parent reply other threads:[~2026-08-22 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 12:16 [PATCH 0/7] docs: core-api: Fix stale function names and a broken example Karl Mehltretter
2026-08-22 12:16 ` [PATCH 1/7] docs: cpu_hotplug: Fix multi-instance removal calls Karl Mehltretter
2026-08-22 17:25 ` Randy Dunlap
2026-08-24 16:57 ` Jonathan Corbet
2026-08-24 18:05 ` Karl Mehltretter
2026-08-24 18:28 ` Jonathan Corbet
2026-08-22 12:16 ` [PATCH 2/7] docs: irq-affinity: Restore grep in example Karl Mehltretter
2026-08-22 17:25 ` Randy Dunlap
2026-08-22 12:16 ` [PATCH 3/7] docs: dma-attributes: Fix dma_alloc_attrs() name Karl Mehltretter
2026-08-22 17:25 ` Randy Dunlap
2026-08-24 9:26 ` Marek Szyprowski
2026-08-22 12:16 ` [PATCH 4/7] docs: swiotlb: Fix maximum mapping size helper Karl Mehltretter
2026-08-22 17:26 ` Randy Dunlap
2026-08-22 12:16 ` Karl Mehltretter [this message]
2026-08-22 16:39 ` [PATCH 5/7] docs: this_cpu_ops: Fix SRCU helper names Paul E. McKenney
2026-08-22 17:28 ` Randy Dunlap
[not found] ` <20260822121651.1559-7-kmehltretter@gmail.com>
2026-08-22 12:28 ` [PATCH 6/7] docs: xarray: Fix xas_try_split() name Zi Yan
2026-08-22 17:30 ` Randy Dunlap
[not found] ` <20260822121651.1559-8-kmehltretter@gmail.com>
2026-08-22 17:32 ` [PATCH 7/7] docs: debugobjects: Fix debug_object_init() name Randy Dunlap
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=20260822121651.1559-6-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=boqun@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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