From: Joe Perches <joe@perches.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: paulmck@linux.vnet.ibm.com, 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: Thu, 10 Jul 2014 03:00:12 -0700 [thread overview]
Message-ID: <1404986412.8839.23.camel@joe-AO725> (raw)
In-Reply-To: <20140710093900.GV3935@laptop>
On Thu, 2014-07-10 at 11:39 +0200, Peter Zijlstra wrote:
> On Wed, Jul 09, 2014 at 06:23:22AM -0700, Joe Perches wrote:
> > > SCHEDULER:
> > > ...
> > > R: Steven Rostedt <rostedt@goodmis.org> (kernel/sched/rt.c)
> > > R: Juri Lelli <jundri.lelli@gmail.com> (kernel/sched/deadline.c)
> >
> > Maybe a better syntax might be something like:
> > R: Steven Rostedt
> > F: kernel/sched/rt.c
> >
> > where optional F:/X: lines override the default
> > assumption of all F:/X: from the section.
>
> Would RF: make sense? Instead of the indenting.
Maybe.
As a preface:
I doubt the need for associating a subset of the files
patterns for a subsystem with a particular reviewer.
If a reviewer is interested enough in a subsystem to
volunteer to read patches then that reviewer likely won't
be overburdened by getting a few more emailed patches
that may be outside a scope of interest.
To answer the question:
If it's done, there needs to be some mechanism to
associate a particular reviewer and the files.
Ordering of "letter:" types in MAINTAINERS is currently
unstructured.
Given a desire to have more than one reviewer interested
in different files, any subset use will either impose some
ordering requirement on the file list or some association
with the reviewer and the reviewer's file patterns of interest.
next prev parent reply other threads:[~2014-07-10 10:00 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 [this message]
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=1404986412.8839.23.camel@joe-AO725 \
--to=joe@perches.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®