From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
mingo@kernel.org
Cc: stern@rowland.harvard.edu, andrea.parri@amarulasolutions.com,
will.deacon@arm.com, 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: LKMM patch status
Date: Mon, 18 Mar 2019 10:50:59 -0700 [thread overview]
Message-ID: <20190318175059.GA3322@linux.ibm.com> (raw)
Hello!
pick 0172d9e32203 tools/memory-model: Rename some RCU relations
pick 284749b0aebb tools/memory-model: Refactor some RCU relations
pick a3f600d92da5 tools/memory-model: Add SRCU support
pick ad9fd20b6dad tools/memory-model: Update README for addition of SRCU
pick 648e717586f2 tools/memory-model: Update Documentation/explanation.txt to include SRCU support
pick 9393998e9ee0 tools/memory-model: Dynamically check SRCU lock-to-unlock matching
pick 034fb712a620 tools/memory-model: Avoid duplicating herdtools versions
Ready to go, sent for inclusion in tip, and will presumably show
up there soon.
http://lkml.kernel.org/r/20190213173650.GA26078@linux.ibm.com
pick 487ecc460732 sched/Documentation/kokr: Update Korean translation to update wake_up() & co. memory-barrier guarantees
pick db467147f131 locking/memory-barriers/kokr: Update Korean translation to replace smp_cond_acquire() with smp_cond_load_acquire()
pick f1887143f598 Documentation/atomic_t: Clarify signed vs unsigned
These have the needed acks/reviews, so I will send them as RFC
patches within the next week or two.
pick ece264389af9 tools/memory-model: Make scripts be executable
pick fd4b7b3c6c0d tools/memory-model: Fix comment in MP+poonceonces.litmus
pick e9cc6e9437e2 tools/memory-model: Do not use "herd" to refer to "herd7"
pick 093e4c7dcf79 docs/memory-barriers.txt: Rewrite "KERNEL I/O BARRIER EFFECTS" section
These all need at least one Reviewed-by or Acked-by.
Thanx, Paul
reply other threads:[~2019-03-18 17:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190318175059.GA3322@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=akiyks@gmail.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=j.alglave@ucl.ac.uk \
--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=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.