From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@kernel.org
Cc: lkmm@lists.linux.dev, Andrea Parri <parri.andrea@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 0/4] tools/memory-model: Documentation updates and fixes
Date: Tue, 18 Mar 2025 11:10:17 +0900 [thread overview]
Message-ID: <62fec120-c95a-4fd2-b7c5-9c24dc58104e@gmail.com> (raw)
In-Reply-To: <5e70aa5f-2c4c-4c0c-971e-82c5bf356cbb@paulmck-laptop>
On Mon, 17 Mar 2025 16:26:34 -0700, Paul E. McKenney wrote:
> On Fri, Mar 14, 2025 at 08:08:24PM +0900, Akira Yokosawa wrote:
>> Hi,
>>
>> While re-reading LKMM documents, I noticed minor issues here and there.
>>
>> This patch set is a collection of updates and fixes resolving them.
>>
>> Patch 1/4 clarifies the relation of locking.txt and recipes.txt.
>> Patches 2/4 and 3/4 are trivial fixes of typos.
>> Patch 4/4 removes a link of MIPS doc which does not work.
>
> Queued and pushed, thank you! I did a bit of wordsmithing and also
> updated to the 2024 LWN API article, so could you please check to see
> whether I messed anything up?
All look good to me!
Thanks, Akira
prev parent reply other threads:[~2025-03-18 2:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 11:08 [PATCH 0/4] tools/memory-model: Documentation updates and fixes Akira Yokosawa
2025-03-14 11:10 ` [PATCH 1/4] tools/memory-model: docs/README: Update introduction of locking.txt Akira Yokosawa
2025-03-14 11:12 ` [PATCH 2/4] tools/memory-model: docs/simple.txt: Fix trivial typos Akira Yokosawa
2025-03-14 11:14 ` [PATCH 3/4] tools/memory-model: docs/ordering: " Akira Yokosawa
2025-03-14 11:15 ` [PATCH 4/4] tools/memory-model: docs/references: Remove broken link to imgtec.com Akira Yokosawa
2025-03-17 23:26 ` [PATCH 0/4] tools/memory-model: Documentation updates and fixes Paul E. McKenney
2025-03-18 2:10 ` Akira Yokosawa [this message]
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=62fec120-c95a-4fd2-b7c5-9c24dc58104e@gmail.com \
--to=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=lkmm@lists.linux.dev \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=stern@rowland.harvard.edu \
/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).