From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, dave@stgolabs.net
Subject: [GIT PULL rcu/next] Additional locktorture commits for 3.18
Date: Sat, 4 Oct 2014 01:50:03 -0700 [thread overview]
Message-ID: <20141004085003.GA17523@linux.vnet.ibm.com> (raw)
Hello, Ingo,
A few additional commits for locktorture for 3.18. These were posted
to LKML at https://lkml.org/lkml/2014/9/29/277 and have been exposed to
-next testing.
These changes are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
for you to fetch changes up to c98fed9fc6a7449affd941d8a8e9fcb0c72977d6:
locktorture: Cleanup header usage (2014-09-30 00:10:02 -0700)
----------------------------------------------------------------
Davidlohr Bueso (4):
locktorture: Support rwlocks
locktorture: Fix __acquire annotation for spinlock irq
locktorture: Cannot hold read and write lock
locktorture: Cleanup header usage
Documentation/locking/locktorture.txt | 5 +
kernel/locking/locktorture.c | 141 ++++++++++++++++++---
.../selftests/rcutorture/configs/lock/CFLIST | 1 +
.../selftests/rcutorture/configs/lock/LOCK04 | 6 +
.../selftests/rcutorture/configs/lock/LOCK04.boot | 1 +
5 files changed, 137 insertions(+), 17 deletions(-)
create mode 100644 tools/testing/selftests/rcutorture/configs/lock/LOCK04
create mode 100644 tools/testing/selftests/rcutorture/configs/lock/LOCK04.boot
next reply other threads:[~2014-10-04 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 8:50 Paul E. McKenney [this message]
2014-10-09 6:40 ` Ingo Molnar
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=20141004085003.GA17523@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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
Powered by JetHome