public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Joe Perches <joe@perches.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, mingo@kernel.org,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
	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 2/3] rcu: Add designated reviewers for RCU
Date: Tue, 8 Jul 2014 13:41:24 -0700	[thread overview]
Message-ID: <20140708204124.GW4603@linux.vnet.ibm.com> (raw)
In-Reply-To: <1404842784.932.22.camel@joe-AO725>

On Tue, Jul 08, 2014 at 11:06:24AM -0700, Joe Perches wrote:
> On Tue, 2014-07-08 at 10:09 +0200, Peter Zijlstra wrote:
> > On Mon, Jul 07, 2014 at 03:42:03PM -0700, Paul E. McKenney wrote:
> > >  MAINTAINERS | 8 ++++++++
> > >  1 file changed, 8 insertions(+)
> > > 
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 1814075c0e74..92f2bf91eec1 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -7405,6 +7405,9 @@ F:	kernel/rcu/torture.c
> > >  
> > >  RCUTORTURE TEST FRAMEWORK
> > >  M:	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > +R:	Steven Rostedt <rostedt@goodmis.org>
> > > +R:	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > > +R:	Lai Jiangshan <laijs@cn.fujitsu.com>
> > >  L:	linux-kernel@vger.kernel.org
> > >  S:	Supported
> > >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> > 
> > OK,.. so if we're going to do this can we talk about the syntax here.
> > 
> > I would like to also use this for SCHED and PERF, but since both are
> > rather big I would like to be able to subdivide things. Now I could of
> > course go create many MAINTAINER sections, but that feels artificial.
> > 
> > So I would like to be able to write:
> > 
> > SCHEDULER:
> > ...
> > R:   Steven Rostedt <rostedt@goodmis.org> (kernel/sched/rt.c)
> > R:   Juri Lelli <juri.lelli@gmail.com>    (kernel/sched/deadline.c)
> > 
> > or something like that. And here I've already done concessions in that
> > the above is machine readable. Ideally I'd be able to say things like:
> > 'for sched and numa related things' add 'rik and mel'.
> > 
> > Hmm, maybe we can look at the patch subject tag like: sched/numa or
> > sched/rt or sched/deadline etc.. instead of the files touched.
> 
> I think it's best to use separate sections.
> 
> The parsing logic in get_maintainers is already ugly enough.

OK, here is a basic change.  Hey, I figure that if you weren't desperately
in need of entertainment, you would not have asked me to hack a perl script!

							Thanx, Paul

------------------------------------------------------------------------

scripts: Teach get_maintainer.pl about the new "R:" tag

We can now designate reviewers in the MAINTAINERS file with the new
"R:" tag, so this commit teaches get_maintainers.pl to add their
email addresses.

Reported-by: Joe Perches <joe@perches.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
index 41987885bd31..03785ce7b5b6 100755
--- a/scripts/get_maintainer.pl
+++ b/scripts/get_maintainer.pl
@@ -536,7 +536,7 @@ sub range_has_maintainer {
 	if ($line =~ m/^(\C):\s*(.*)/) {
 	    my $type = $1;
 	    my $value = $2;
-	    if ($type eq 'M') {
+	    if ($type eq 'M' || $type eq 'R') {
 		return 1;
 	    }
 	}
@@ -1047,7 +1047,7 @@ sub add_categories {
 			}
 		    }
 		}
-	    } elsif ($ptype eq "M") {
+	    } elsif ($ptype eq "M" || $ptype eq "R") {
 		my ($name, $address) = parse_email($pvalue);
 		if ($name eq "") {
 		    if ($i > 0) {
@@ -1062,7 +1062,11 @@ sub add_categories {
 		}
 		if ($email_maintainer) {
 		    my $role = get_maintainer_role($i);
-		    push_email_addresses($pvalue, $role);
+		    if ($ptype eq "M") {
+		      push_email_addresses($pvalue, $role);
+		    } else {
+		      push_email_addresses($pvalue, "designated reviewer");
+		    }
 		}
 	    } elsif ($ptype eq "T") {
 		push(@scm, $pvalue);


  reply	other threads:[~2014-07-08 20:41 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 [this message]
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
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=20140708204124.GW4603@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=joe@perches.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