From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
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, dhowells@redhat.com, edumazet@google.com,
dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
sbw@mit.edu
Subject: Re: [PATCH tip/core/rcu 3/3] rcu: Update RCU maintainership
Date: Tue, 8 Jul 2014 13:47:09 -0700 [thread overview]
Message-ID: <20140708204709.GX4603@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140708175855.GA2927@jtriplet-mobl1>
On Tue, Jul 08, 2014 at 10:58:55AM -0700, Josh Triplett wrote:
> On Mon, Jul 07, 2014 at 03:42:04PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> >
> > Drop Dipankar Sarma at his request (https://lkml.org/lkml/2014/6/2/628),
> > add Josh Triplett based on long-term review, contributions, and
> > agreement to take on this role (https://lkml.org/lkml/2014/6/2/554).
> >
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> Reviewed-by: Josh Triplett <josh@joshtriplett.org>
Got it, thank you!
> Does it make sense to keep separate entries for each of these, at this
> point, or should we just merge all of them into the main "READ-COPY
> UPDATE (RCU)" entry?
Good question! Let's see how we feel about it now, and then again a
year from now.
Thanx, Paul
> > MAINTAINERS | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 92f2bf91eec1..922661d17083 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -7405,6 +7405,7 @@ F: kernel/rcu/torture.c
> >
> > RCUTORTURE TEST FRAMEWORK
> > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > +M: Josh Triplett <josh@joshtriplett.org>
> > R: Steven Rostedt <rostedt@goodmis.org>
> > R: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > R: Lai Jiangshan <laijs@cn.fujitsu.com>
> > @@ -7430,8 +7431,8 @@ S: Supported
> > F: net/rds/
> >
> > READ-COPY UPDATE (RCU)
> > -M: Dipankar Sarma <dipankar@in.ibm.com>
> > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > +M: Josh Triplett <josh@joshtriplett.org>
> > R: Steven Rostedt <rostedt@goodmis.org>
> > R: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > R: Lai Jiangshan <laijs@cn.fujitsu.com>
> > @@ -8214,6 +8215,7 @@ F: mm/sl?b.c
> > SLEEPABLE READ-COPY UPDATE (SRCU)
> > M: Lai Jiangshan <laijs@cn.fujitsu.com>
> > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > +M: Josh Triplett <josh@joshtriplett.org>
> > R: Steven Rostedt <rostedt@goodmis.org>
> > R: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > L: linux-kernel@vger.kernel.org
> > --
> > 1.8.1.5
> >
>
next prev parent reply other threads:[~2014-07-08 20:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 22:41 [PATCH tip/core/rcu 0/3] Maintainership changes for 3.17 Paul E. McKenney
2014-07-07 22:42 ` [PATCH tip/core/rcu 1/3] MAINTAINERS: Add "R:" designated-reviewers tag Paul E. McKenney
2014-07-07 22:42 ` [PATCH tip/core/rcu 2/3] rcu: Add designated reviewers for RCU Paul E. McKenney
2014-07-08 8:09 ` Peter Zijlstra
2014-07-08 18:06 ` Joe Perches
2014-07-08 20:41 ` Paul E. McKenney
2014-07-08 21:01 ` Joe Perches
2014-07-08 21:52 ` Paul E. McKenney
2014-07-08 22:05 ` Joe Perches
2014-07-08 22:25 ` Paul E. McKenney
2014-07-09 4:09 ` Joe Perches
2014-07-09 11:14 ` Paul E. McKenney
2014-07-09 13:23 ` Joe Perches
2014-07-10 9:39 ` Peter Zijlstra
2014-07-10 10:00 ` Joe Perches
2014-07-10 23:16 ` josh
2014-07-11 8:32 ` Peter Zijlstra
2014-07-09 17:00 ` josh
2014-07-09 17:13 ` Joe Perches
2014-07-09 17:42 ` Frederic Weisbecker
2014-07-09 18:10 ` Joe Perches
2014-07-07 22:42 ` [PATCH tip/core/rcu 3/3] rcu: Update RCU maintainership Paul E. McKenney
2014-07-08 17:58 ` Josh Triplett
2014-07-08 20:47 ` Paul E. McKenney [this message]
2014-07-07 22:55 ` [PATCH tip/core/rcu 0/3] Maintainership changes for 3.17 Joe Perches
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=20140708204709.GX4603@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=niv@us.ibm.com \
--cc=oleg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox