From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, lkmm@lists.linux.dev,
kernel-team@meta.com, akiyks@gmail.com, urezki@gmail.com
Subject: [GIT PULL] LKMM changes for v6.16
Date: Sun, 25 May 2025 21:41:36 -0700 [thread overview]
Message-ID: <737fd7ca-57d8-47cc-b6d4-e3e701ffc733@paulmck-laptop> (raw)
Hello, Linus,
When the v6.16 merge window opens, please pull this LKMM update from:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/lkmm.2025.05.25a
# HEAD: 5c9e0062989e5d2bd77b75c432b54e8ec7689bc7: tools/memory-model/Documentation: Fix SRCU section in explanation.txt (2025-04-23 12:17:04 -0700)
----------------------------------------------------------------
lkmm: Update documentation
Changes
-------
* Cross-references, typos, broken URLs (Akira Yokosawa)
* Clarify SRCU explanation (Uladzislau Rezki)
----------------------------------------------------------------
Akira Yokosawa (4):
tools/memory-model: docs/README: Update introduction of locking.txt
tools/memory-model: docs/simple.txt: Fix trivial typos
tools/memory-model: docs/ordering: Fix trivial typos
tools/memory-model: docs/references: Remove broken link to imgtec.com
Uladzislau Rezki (Sony) (1):
tools/memory-model/Documentation: Fix SRCU section in explanation.txt
tools/memory-model/Documentation/README | 7 +++++--
tools/memory-model/Documentation/explanation.txt | 2 +-
tools/memory-model/Documentation/locking.txt | 5 +++++
tools/memory-model/Documentation/ordering.txt | 22 +++++++++++-----------
tools/memory-model/Documentation/recipes.txt | 4 ++++
tools/memory-model/Documentation/references.txt | 3 +--
tools/memory-model/Documentation/simple.txt | 4 ++--
7 files changed, 29 insertions(+), 18 deletions(-)
next reply other threads:[~2025-05-26 4:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 4:41 Paul E. McKenney [this message]
2025-05-27 18:30 ` [GIT PULL] LKMM changes for v6.16 pr-tracker-bot
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=737fd7ca-57d8-47cc-b6d4-e3e701ffc733@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmm@lists.linux.dev \
--cc=torvalds@linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).