From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com
Subject: Re: [PATCH tip/core/rcu 0/4] torture-test changes for 4.4
Date: Tue, 6 Oct 2015 10:33:30 -0700 [thread overview]
Message-ID: <20151006173330.GH9600@cloud> (raw)
In-Reply-To: <20151006164855.GA17055@linux.vnet.ibm.com>
On Tue, Oct 06, 2015 at 09:48:55AM -0700, Paul E. McKenney wrote:
> Hello!
>
> This series contains torture-test changes:
>
> 1. Fix module unwind when bad torture_type specified to rcutorture.
>
> 2. Fix unused-function warning for torturing_tasks().
>
> 3. Forgive non-plural arguments.
>
> 4. Fix module unwind when bad torture_type specified to locktorture.
For all four:
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
prev parent reply other threads:[~2015-10-06 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 16:48 [PATCH tip/core/rcu 0/4] torture-test changes for 4.4 Paul E. McKenney
2015-10-06 16:49 ` [PATCH tip/core/rcu 1/4] rcutorture: Fix module unwind when bad torture_type specified Paul E. McKenney
2015-10-06 16:49 ` [PATCH tip/core/rcu 2/4] rcutorture: Fix unused-function warning for torturing_tasks() Paul E. McKenney
2015-10-06 16:49 ` [PATCH tip/core/rcu 3/4] torture: Forgive non-plural arguments Paul E. McKenney
2015-10-06 16:49 ` [PATCH tip/core/rcu 4/4] locktorture: Fix module unwind when bad torture_type specified Paul E. McKenney
2015-10-06 17:32 ` [PATCH tip/core/rcu 1/4] rcutorture: " Josh Triplett
2015-10-06 18:32 ` Paul E. McKenney
2015-10-06 17:33 ` Josh Triplett [this message]
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=20151006173330.GH9600@cloud \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.