From: joe@perches•com (Joe Perches)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] MAINTAINERS: Start using the 'reviewer' (R) tag
Date: Tue, 27 Oct 2015 11:44:42 -0700 [thread overview]
Message-ID: <1445971482.2757.27.camel@perches.com> (raw)
In-Reply-To: <20151027181555.GE5828@x1>
On Tue, 2015-10-27 at 18:15 +0000, Lee Jones wrote:
> On Tue, 27 Oct 2015, Sebastian Reichel wrote:
> > On Tue, Oct 27, 2015 at 03:42:37PM +0000, Lee Jones wrote:
> > > Since eafbaac ("MAINTAINERS: Add "R:" designated-reviewers tag") we
> > > have been able to tag specific people as Reviewers. These are key
> > > individuals who are tasked with or volunteer to review code submitted
> > > to a subsystem or specific file. However, according to MAINTAINERS
> > > we have 1046 Maintainers and only a mere 22 Reviewers. I believe
> > > these numbers to be incorrect, as many of these Maintainers are in
> > > fact Reviewers.
Most entries in MAINTAINERS seem to be vanity entries than actual
active participants. A person typically writes a driver, adds a
MAINTAINER entry, then forgets about it and/or the hardware becomes
outdated.
> > > I have taken the time to identify some of the Reviewers who pertain
> > > to subsystems which I look after, and have changed their status from
> > > Maintainer (collector of patches) to Reviewer (reviewer of code).
> >
> > [for drivers/power/*]
> > Acked-By: Sebastian Reichel <sre@kernel•org>
>
> Thanks.
>
> > I think you should CC the people, which are changed from "M:" to
> > "R:", though.
>
> Yes, makes sense.
>
> I'd like to collect some Maintainer Acks first though.
I think people from organizations like Samsung are actual
maintainers not reviewers.
Their drivers are not thrown over a wall and forgotten.
next prev parent reply other threads:[~2015-10-27 18:44 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 15:42 [PATCH] MAINTAINERS: Start using the 'reviewer' (R) tag Lee Jones
2015-10-27 17:24 ` Sebastian Reichel
2015-10-27 18:15 ` Lee Jones
2015-10-27 18:44 ` Joe Perches [this message]
2015-10-28 1:46 ` Krzysztof Kozlowski
2015-10-28 8:24 ` Lee Jones
2015-10-28 9:21 ` Javier Martinez Canillas
2015-10-28 9:25 ` Javier Martinez Canillas
2015-10-28 9:31 ` Krzysztof Kozlowski
2015-10-28 10:28 ` Lee Jones
2015-10-28 10:53 ` Javier Martinez Canillas
2015-10-28 11:06 ` Joe Perches
2015-10-28 11:25 ` Javier Martinez Canillas
2015-10-28 11:39 ` Lee Jones
2015-10-28 12:14 ` Lee Jones
2015-10-28 12:20 ` Joe Perches
2015-10-28 12:24 ` Lee Jones
2015-10-28 12:46 ` Joe Perches
2015-10-28 13:06 ` Javier Martinez Canillas
2015-10-28 13:34 ` Lee Jones
2015-10-28 14:09 ` Javier Martinez Canillas
2015-10-28 14:38 ` Lee Jones
2015-10-28 14:54 ` Javier Martinez Canillas
2015-10-28 23:56 ` Krzysztof Kozlowski
2015-10-29 0:12 ` Javier Martinez Canillas
2015-10-30 16:51 ` Lee Jones
2015-10-30 16:51 ` Lee Jones
2015-10-28 9:23 ` Krzysztof Kozlowski
2015-10-28 9:39 ` Uwe Kleine-König
2015-10-28 9:55 ` Lee Jones
2015-10-28 13:13 ` Krzysztof Kozlowski
2015-10-28 16:41 ` [PATCH] get_maintainer: Add subsystem to reviewer output Joe Perches
2015-10-28 17:01 ` Lee Jones
2015-10-28 17:08 ` Joe Perches
2015-10-28 17:22 ` Lee Jones
2015-10-28 17:30 ` Joe Perches
2015-10-28 17:49 ` Lee Jones
2015-10-28 17:56 ` Joe Perches
2015-10-29 9:20 ` Lee Jones
2015-10-29 14:14 ` Joe Perches
2015-10-29 16:17 ` Lee Jones
2015-10-28 17:18 ` Joe Perches
2015-10-28 23:49 ` Krzysztof Kozlowski
2015-10-28 10:14 ` [PATCH] MAINTAINERS: Start using the 'reviewer' (R) tag Lee Jones
2015-10-28 13:27 ` Krzysztof Kozlowski
2015-10-28 13:49 ` Lee Jones
2015-10-28 16:26 ` Bartlomiej Zolnierkiewicz
2015-10-28 16:33 ` Lee Jones
2015-10-28 8:57 ` Chanwoo Choi
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=1445971482.2757.27.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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