From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>, Marco Elver <elver@google.com>
Cc: Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
Daniel Lustig <dlustig@nvidia.com>,
Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Andrea Parri <parri.andrea@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH lkmm 0/2] tools/memory-model: Add locking.txt and glossary.txt to README
Date: Fri, 21 Jun 2024 13:08:24 +0900 [thread overview]
Message-ID: <ae2b0f62-a593-4e7c-ab51-06d4e8a21005@gmail.com> (raw)
Hi all,
[+CC: Marco, as Patch 1/2 includes update related to access-marking.txt.]
Looks to me like Andrea's herd-representation.txt has stabilized.
Patch 1/2 fills missing pieces in docs/README.
While skimming through documents, I noticed a typo in simple.txt.
Patch 2/2 fixes it.
Thanks, Akira
--
Akira Yokosawa (2):
tools/memory-model: Add locking.txt and glossary.txt to README
tools/memory-model: simple.txt: Fix dangling reference to
recipes-pairs.txt
tools/memory-model/Documentation/README | 17 +++++++++++++++++
tools/memory-model/Documentation/simple.txt | 2 +-
2 files changed, 18 insertions(+), 1 deletion(-)
base-commit: 662b960d12d280476c4b09070ed6c4b808ee91da
--
2.34.1
next reply other threads:[~2024-06-21 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 4:08 Akira Yokosawa [this message]
2024-06-21 4:10 ` [PATCH lkmm 1/2] tools/memory-model: Add locking.txt and glossary.txt to README Akira Yokosawa
2024-06-21 4:12 ` [PATCH lkmm 2/2] tools/memory-model: simple.txt: Fix stale reference to recipes-pairs.txt Akira Yokosawa
2024-06-21 8:23 ` [PATCH lkmm 0/2] tools/memory-model: Add locking.txt and glossary.txt to README Andrea Parri
2024-06-21 9:34 ` Akira Yokosawa
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=ae2b0f62-a593-4e7c-ab51-06d4e8a21005@gmail.com \
--to=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=elver@google.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@kernel.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