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.