From: Andrea Parri <parri.andrea@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
kernel-team@fb.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,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Christoph Hellwig <hch@lst.de>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: LKMM patches for next merge window
Date: Thu, 25 Jun 2020 01:24:02 +0200 [thread overview]
Message-ID: <20200624232402.GA465543@andrea> (raw)
In-Reply-To: <20200624185400.GA13594@paulmck-ThinkPad-P72>
On Wed, Jun 24, 2020 at 11:54:00AM -0700, Paul E. McKenney wrote:
> Hello!
>
> Here is the list of LKMM patches I am considering for the next merge
> window and the status of each. Any I am missing or any that need to
> wait or be modified?
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> 3ce5d69 docs: fix references for DMA*.txt files
> Could someone please provide an ack?
Fixing the N-th commit "move docs without updating in-tree references".
;-/
Most importantly there appears to be some on-going discussion about it,
cf.
https://lkml.kernel.org/r/20200623072240.GA974@lst.de
(could you please sort this out?)
Andrea
>
> ac1a749 tools/memory-model: Add recent references
> be1ce3e tools/memory-model: Fix "conflict" definition
> 24dca63 Documentation: LKMM: Add litmus test for RCU GP guarantee where updater frees object
> 47ec95b Documentation: LKMM: Add litmus test for RCU GP guarantee where reader stores
> bb2c938 MAINTAINERS: Update maintainers for new Documentation/litmus-tests
> 05bee9a tools/memory-model: Add an exception for limitations on _unless() family
> dc76257 Documentation/litmus-tests: Introduce atomic directory
> d059e50 Documentation/litmus-tests/atomic: Add a test for atomic_set()
> 7eecf76 Documentation/litmus-tests/atomic: Add a test for smp_mb__after_atomic()
> 116f054 tools/memory-model: Fix reference to litmus test in recipes.txt
> ffd32d4 Documentation/litmus-tests: Merge atomic's README into top-level one
> a08ae99 Documentation/litmus-tests: Cite an RCU litmus test
> 843285eb tools/memory-model/README: Expand dependency of klitmus7
> 0296c57 tools/memory-model/README: Mention herdtools7 7.56 in compatibility table
> 47e4f0a Documentation/litmus-tests: Add note on herd7 7.56 in atomic litmus test
> All ready to go.
next prev parent reply other threads:[~2020-06-24 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 18:54 LKMM patches for next merge window Paul E. McKenney
2020-06-24 23:24 ` Andrea Parri [this message]
2020-06-25 16:33 ` Paul E. McKenney
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=20200624232402.GA465543@andrea \
--to=parri.andrea@gmail.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--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=mchehab+huawei@kernel.org \
--cc=mingo@kernel.org \
--cc=npiggin@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