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: josh@joshtriplett.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,
	niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org,
	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 RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag
Date: Mon, 2 Jun 2014 11:16:58 -0700	[thread overview]
Message-ID: <20140602181658.GX22231@linux.vnet.ibm.com> (raw)
In-Reply-To: <1401731968.7323.4.camel@joe-AO725>

On Mon, Jun 02, 2014 at 10:59:28AM -0700, Joe Perches wrote:
> On Mon, 2014-06-02 at 10:48 -0700, josh@joshtriplett.org wrote:
> > On Mon, Jun 02, 2014 at 10:22:58AM -0700, Joe Perches wrote:
> > > On Mon, 2014-06-02 at 10:00 -0700, Paul E. McKenney wrote:
> > > > A ksummit-discuss email thread looked at the difficulty recruiting
> > > > and retaining reviewers.
> > > 
> > > []
> > > 
> > > > Paul Walmsley also noted the need for patch
> > > > submitters to know who the key reviewers are and suggested adding an
> > > > "R:" tag to the MAINTAINERS file to record this information on a
> > > > per-subsystem basis.
> > > 
> > > I'm not sure of the value of this.
> > > 
> > > Why not just mark the actual reviewers as maintainers?
> > 
> > As discussed in the kernel summit discussion, being a regular patch
> > reviewer isn't the same thing as being *the* maintainer.
> 
> I think it's not particularly important or valuable
> here to make that distinction.
> 
> What real difference does it make?

In the particular case of Josh, none, at least from my viewpoint.  He of
course might or might not want to take on additional maintainership
responsibility at this particular point in time, in which case, I would
be more than happy to have him as a designated maintainer.

But there have been people who have found serious issues in RCU patches
who I would not trust as full maintainers.  The ability to find defects
is valuable in and of itself, and should be recognized as such, even
when not accompanied by the rest of the maintainership package.

							Thanx, Paul


  parent reply	other threads:[~2014-06-02 18:17 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 17:00 [PATCH RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag Paul E. McKenney
2014-06-02 17:00 ` [PATCH RFC 2/2] rcu: Add Josh Triplett as designated reviewer Paul E. McKenney
2014-06-02 20:35   ` Andrew Morton
2014-06-02 20:36     ` Joe Perches
2014-06-02 20:38       ` Randy Dunlap
2014-06-03  0:02         ` josh
2014-06-03  1:07           ` Randy Dunlap
2014-06-03  1:51             ` Josh Triplett
2014-06-03  3:11               ` Joe Perches
2014-06-03  5:10                 ` Josh Triplett
2014-06-03  5:21                   ` Joe Perches
2014-06-03 17:21               ` Randy Dunlap
2014-06-02 17:22 ` [PATCH RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag Joe Perches
2014-06-02 17:29   ` Steven Rostedt
2014-06-02 17:34     ` Joe Perches
2014-06-02 17:48   ` josh
2014-06-02 17:59     ` Joe Perches
2014-06-02 18:12       ` Josh Boyer
2014-06-02 18:15         ` Joe Perches
2014-06-02 18:16       ` Paul E. McKenney [this message]
2014-06-02 18:44         ` Joe Perches
2014-06-02 18:50           ` Steven Rostedt
2014-06-02 18:55             ` josh
2014-06-02 19:05               ` Joe Perches
2014-06-02 19:09                 ` josh
2014-06-02 19:17                   ` Joe Perches
2014-06-02 23:19                     ` Dave Chinner
2014-06-02 23:24                       ` Andrew Morton
2014-06-03  0:35                         ` Steven Rostedt
2014-06-02 23:59                       ` josh
2014-06-03  0:12                         ` Joe Perches
2014-06-03 23:48                           ` Ken Moffat
2014-06-04  0:03                             ` Steven Rostedt
2014-06-04  0:33                             ` Joe Perches
2014-06-03  1:11                         ` Dave Chinner
2014-06-03  1:30                           ` Steven Rostedt
2014-06-03  7:16                             ` Dave Chinner
2014-06-03 13:24                               ` Mathieu Desnoyers
2014-06-03 15:54                                 ` Paul E. McKenney
2014-06-03 17:43                               ` Steven Rostedt
2014-06-03 18:05                                 ` Randy Dunlap
2014-06-03 20:52                                 ` Theodore Ts'o
2014-06-03 21:46                                   ` Steven Rostedt
2014-06-03 22:08                                     ` josh
2014-06-05  4:01                                 ` Dave Chinner
2014-06-05 21:14                                   ` Frank Rowand
2014-06-02 19:26                 ` Paul E. McKenney
2014-06-02 20:41                   ` Dipankar Sarma
2014-06-02 19:07             ` Paul E. McKenney
2014-06-02 18:56         ` josh
2014-06-02 19:08           ` Paul E. McKenney
2014-06-02 19:11             ` josh
2014-06-02 19:27               ` Paul E. McKenney
2014-06-02 19:36                 ` Joe Perches
2014-06-02 19:40                   ` Randy Dunlap
2014-06-02 20:29                     ` josh
2014-06-02 19:50                   ` Paul E. McKenney
2014-06-02 19:55                     ` Joe Perches
2014-06-02 20:07                       ` Paul E. McKenney
2014-06-02 20:25                 ` Mathieu Desnoyers
2014-06-03 15:37                   ` Paul E. McKenney
2014-06-03 16:16                     ` Steven Rostedt
2014-06-03 16:25                       ` Paul E. McKenney
2014-06-04  1:35                 ` Lai Jiangshan

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=20140602181658.GX22231@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