From: "Paul E. McKenney" <paulmck@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
kernel-team@fb.com, mingo@kernel.org, parri.andrea@gmail.com,
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 memory-model] Add recent references
Date: Mon, 17 Feb 2020 11:12:45 -0800 [thread overview]
Message-ID: <20200217191245.GV2935@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <Pine.LNX.4.44L0.2002161158140.30459-100000@netrider.rowland.org>
On Sun, Feb 16, 2020 at 12:01:14PM -0500, Alan Stern wrote:
> On Fri, 14 Feb 2020, Paul E. McKenney wrote:
>
> > This commit updates the list of LKMM-related publications in
> > Documentation/references.txt.
> >
> > Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
>
> > o Paul E. McKenney, Ulrich Weigand, Andrea Parri, and Boqun
> > - Feng. 2016. "Linux-Kernel Memory Model". (6 June 2016).
> > - http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0124r2.html.
> > + Feng. 2018. "Linux-Kernel Memory Model". (27 September 2018).
> > + http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0124r6.html.
>
> Even though this is an update, the new version referenced here is
> already out-of-date (in particular, with regard to its discussions of
> the ordering properties of unlock-lock sequences as viewed by threads
> not holding the lock). And it contains a few typos scattered
> throughout.
Indeed, 18 months is a long time for LKMM, isn't it? ;-)
Sounds like time to update it for the next meeting. I of course would
welcome any notes you might have taken while going through it.
Thanx, Paul
prev parent reply other threads:[~2020-02-17 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 23:31 [PATCH memory-model] Add recent references Paul E. McKenney
2020-02-16 0:58 ` Andrea Parri
2020-02-16 13:51 ` Paul E. McKenney
2020-02-16 17:01 ` Alan Stern
2020-02-17 19:12 ` 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=20200217191245.GV2935@paulmck-ThinkPad-P72 \
--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@fb.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 NNTP newsgroup(s).