From: "Paul E. McKenney" <paulmck@kernel.org>
To: Andrea Parri <parri.andrea@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
lkmm@lists.linux.dev, kernel-team@meta.com, mingo@kernel.org,
stern@rowland.harvard.edu, will@kernel.org, peterz@infradead.org,
boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com,
j.alglave@ucl.ac.uk, luc.maranget@inria.fr, akiyks@gmail.com
Subject: Re: [PATCH 0/4] LKMM documentation updates for v6.16
Date: Fri, 18 Apr 2025 13:31:28 -0700 [thread overview]
Message-ID: <67aebf50-68a7-459d-819b-13b9721ec051@paulmck-laptop> (raw)
In-Reply-To: <aAKaAXQApP8JoQkL@andrea>
On Fri, Apr 18, 2025 at 08:30:42PM +0200, Andrea Parri wrote:
> On Fri, Apr 18, 2025 at 10:29:53AM -0700, Paul E. McKenney wrote:
> > Hello!
> >
> > This series provides the following documentation updates, all courtesy
> > of Akira Yokosawa:
> >
> > 1. docs/README: Update introduction of locking.txt.
> >
> > 2. docs/simple.txt: Fix trivial typos.
> >
> > 3. docs/ordering: Fix trivial typos.
> >
> > 4. docs/references: Remove broken link to imgtec.com.
>
> Thanks for the updates; for this series,
>
> Acked-by: Andrea Parri <parri.andrea@gmail.com>
Thank you! I will apply this on my next rebase.
Thanx, Paul
prev parent reply other threads:[~2025-04-18 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 17:29 [PATCH 0/4] LKMM documentation updates for v6.16 Paul E. McKenney
2025-04-18 17:29 ` [PATCH 1/4] tools/memory-model: docs/README: Update introduction of locking.txt Paul E. McKenney
2025-04-18 17:29 ` [PATCH 2/4] tools/memory-model: docs/simple.txt: Fix trivial typos Paul E. McKenney
2025-04-18 17:29 ` [PATCH 3/4] tools/memory-model: docs/ordering: " Paul E. McKenney
2025-04-18 17:30 ` [PATCH 4/4] tools/memory-model: docs/references: Remove broken link to imgtec.com Paul E. McKenney
2025-04-18 18:30 ` [PATCH 0/4] LKMM documentation updates for v6.16 Andrea Parri
2025-04-18 20:31 ` Paul E. McKenney [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=67aebf50-68a7-459d-819b-13b9721ec051@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=j.alglave@ucl.ac.uk \
--cc=kernel-team@meta.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmm@lists.linux.dev \
--cc=luc.maranget@inria.fr \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).