From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, corbet@lwn.net, peterz@infradead.org,
linux-doc@vger.kernel.org, dhowells@redhat.com,
will.deacon@arm.com, dave@stgolabs.net
Subject: [PATCH locking 0/4] locktorture and memory-barriers.txt updates
Date: Tue, 26 Apr 2016 10:20:41 -0700 [thread overview]
Message-ID: <20160426172041.GA4539@linux.vnet.ibm.com> (raw)
Hello!
This series contains a few memory-barriers.txt updates and a locktorture
cleanup:
1. Add a disclaimer to memory-barrier.txt, courtesy of
Peter Zijlstra.
2. Explicitly state the purpose of memory-barrier.txt, courtesy
of David Howells.
3. Explicitly state that ACQUIRE applies to loads and that
RELEASE applies to stores, courtesy of Will Deacon.
4. Simplify torture_runnable computation in locktorture, replacing
a multiline #ifdef with an IS_ENABLED() that fits into an
existing line.
Thanx, Paul
------------------------------------------------------------------------
Documentation/memory-barriers.txt | 39 +++++++++++++++++++++++++++++++++++++-
kernel/locking/locktorture.c | 7 ------
2 files changed, 39 insertions(+), 7 deletions(-)
next reply other threads:[~2016-04-26 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 17:20 Paul E. McKenney [this message]
2016-04-26 17:22 ` [PATCH locking 1/4] documentation: Add disclaimer Paul E. McKenney
2016-04-28 10:27 ` [tip:locking/core] locking/Documentation: " tip-bot for Peter Zijlstra
2016-04-26 17:22 ` [PATCH locking 2/4] documentation: State purpose of memory-barriers.txt Paul E. McKenney
2016-04-28 10:28 ` [tip:locking/core] locking/Documentation: " tip-bot for David Howells
2016-04-26 17:22 ` [PATCH locking 3/4] documentation: ACQUIRE applies to loads, RELEASE applies to stores Paul E. McKenney
2016-04-28 10:28 ` [tip:locking/core] locking/Documentation: Clarify that " tip-bot for Will Deacon
2016-04-26 17:22 ` [PATCH locking 4/4] locktorture: Simplify torture_runnable computation Paul E. McKenney
2016-04-28 10:29 ` [tip:locking/core] lcoking/locktorture: Simplify the " tip-bot for 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=20160426172041.GA4539@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=dhowells@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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.