From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, Valdis.Kletnieks@vt.edu,
dhowells@redhat.com, edumazet@google.com, darren@dvhart.com,
fweisbec@gmail.com, sbw@mit.edu
Subject: Re: [PATCH tip/core/rcu 0/2] v2 Tiny RCU changes for 3.9
Date: Sun, 27 Jan 2013 21:58:40 +1100 [thread overview]
Message-ID: <20130127105840.GF3119@leaf> (raw)
In-Reply-To: <20130127002328.GA4847@linux.vnet.ibm.com>
On Sat, Jan 26, 2013 at 04:23:28PM -0800, Paul E. McKenney wrote:
> Hello!
>
> This series provides a couple of tiny-RCU changes:
>
> 1. Make Tiny RCU emit RCU CPU stall warnings when RCU_TRACE=y.
> 2. Allow TREE_PREEMPT_RCU to be used on UP systems.
I replied to patch 1 with a suggestion; with that change,
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
for the whole series.
- Josh Triplett
prev parent reply other threads:[~2013-01-27 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 0:23 [PATCH tip/core/rcu 0/2] v2 Tiny RCU changes for 3.9 Paul E. McKenney
2013-01-27 0:23 ` [PATCH tip/core/rcu 1/2] rcu: Provide RCU CPU stall warnings for tiny RCU Paul E. McKenney
2013-01-27 0:23 ` [PATCH tip/core/rcu 2/2] rcu: Allow TREE_PREEMPT_RCU on UP systems Paul E. McKenney
2013-01-27 10:58 ` Josh Triplett
2013-01-27 10:57 ` [PATCH tip/core/rcu 1/2] rcu: Provide RCU CPU stall warnings for tiny RCU Josh Triplett
2013-01-29 5:56 ` Paul E. McKenney
2013-01-27 10:58 ` 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=20130127105840.GF3119@leaf \
--to=josh@joshtriplett.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--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.