[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1404842784.932.22.camel@joe-AO725>
Date: Tue, 08 Jul 2014 11:06:24 -0700
From: Joe Perches <joe@...ches.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, mingo@...nel.org,
laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
dvhart@...ux.intel.com, fweisbec@...il.com, oleg@...hat.com,
sbw@....edu
Subject: Re: [PATCH tip/core/rcu 2/3] rcu: Add designated reviewers for RCU
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@...ux.vnet.ibm.com>
> > +R: Steven Rostedt <rostedt@...dmis.org>
> > +R: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
> > +R: Lai Jiangshan <laijs@...fujitsu.com>
> > L: linux-kernel@...r.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@...dmis.org> (kernel/sched/rt.c)
> R: Juri Lelli <juri.lelli@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists