linux-kernel - Re: [PATCH tip/core/rcu 2/3] rcu: Add designated reviewers for RCU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1404986412.8839.23.camel@joe-AO725>
Date:	Thu, 10 Jul 2014 03:00:12 -0700
From:	Joe Perches <joe@...ches.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	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 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@...dmis.org> (kernel/sched/rt.c)
> > > R:   Juri Lelli <jundri.lelli@...il.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.

--
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/