From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Akira Yokosawa <akiyks@gmail.com>,
Andrea Parri <andrea.parri@amarulasolutions.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, boqun.feng@gmail.com,
dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
npiggin@gmail.com, peterz@infradead.org, will.deacon@arm.com,
dlustig@nvidia.com
Subject: Re: LKMM patch scorecard for v4.19 merge window
Date: Mon, 9 Jul 2018 16:01:36 -0700 [thread overview]
Message-ID: <20180709230136.GO3593@linux.vnet.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1807091418022.2462-100000@iolanthe.rowland.org>
On Mon, Jul 09, 2018 at 02:18:53PM -0400, Alan Stern wrote:
> On Fri, 6 Jul 2018, Paul E. McKenney wrote:
>
> > Hello!
> >
> > Here is the updated scorecard:
> >
> > e9ff68680cd4 tools/memory-model: Add litmus test for full multicopy atomicity
> > c21fcc6594f1 tools/memory-model: Fix ISA2+pooncelock+pooncelock+pombonce name
> > 2f5a1b9b74a2 MAINTAINERS: Add Daniel Lustig as an LKMM reviewer
> > e1c071fab8e1 locking/memory-barriers.txt/kokr: Update Korean translation to fix broken DMA vs. MMIO ordering example
> > b95546bdac98 tools/memory-model: Remove ACCESS_ONCE() from recipes
> > a1e5fd06bb6b tools/memory-model: Remove ACCESS_ONCE() from model
> > a54df4f2be14 tools/memory-model: Make scripts executable
> > c6b04f78bf25 docs: atomic_ops: Describe atomic_set as a write operation
> > 36853a86cf04 tools/memory-model: Add informal LKMM documentation to MAINTAINERS
> > 950ba9d5bb8f sched: Use smp_mb() in wake_woken_function()
> > c7af75d2ba8b locking: Clarify requirements for smp_mb__after_spinlock()
> > bc8209732066 doc: Update wake_up() & co. memory-barrier guarantees
> >
> > All of these are ready for the upcoming merge window,
> > thanks everyone!
> >
> > 473fd6e42ddc tools/memory-model: Rename litmus tests to comply to norm7
> >
> > This one still needs an ack.
>
> I have audited this patch.
>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
Thank you, Alan! I will apply this as part of my next rebase and promote
this patch to the queue for the upcoming grace period.
Thanx, Paul
next prev parent reply other threads:[~2018-07-09 22:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 12:33 [PATCH 0/2] tools/memory-model: remove ACCESS_ONCE() Mark Rutland
2018-06-28 12:33 ` [PATCH 1/2] tools/memory-model: remove ACCESS_ONCE() from recipes Mark Rutland
2018-06-28 12:33 ` [PATCH 2/2] tools/memory-model: remove ACCESS_ONCE() from model Mark Rutland
2018-06-28 12:38 ` [PATCH 0/2] tools/memory-model: remove ACCESS_ONCE() Andrea Parri
2018-06-28 15:21 ` Paul E. McKenney
2018-06-28 16:51 ` Andrea Parri
2018-07-02 18:54 ` Paul E. McKenney
2018-07-03 10:12 ` Andrea Parri
2018-07-03 15:53 ` Paul E. McKenney
2018-07-03 17:23 ` Andrea Parri
2018-07-06 14:55 ` Paul E. McKenney
2018-06-28 22:22 ` Akira Yokosawa
2018-06-29 3:05 ` Paul E. McKenney
2018-07-07 0:17 ` LKMM patch scorecard for v4.19 merge window Paul E. McKenney
2018-07-09 18:18 ` Alan Stern
2018-07-09 23:01 ` Paul E. McKenney [this message]
2018-07-10 20:05 ` 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=20180709230136.GO3593@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mark.rutland@arm.com \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.