From: Joe Perches <joe@perches.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: MAINTAINERS without commits in the last 3 years
Date: Fri, 26 Aug 2016 10:09:23 -0700 [thread overview]
Message-ID: <1472231363.4914.49.camel@perches.com> (raw)
In-Reply-To: <0c04b145-4322-c1e7-2a77-b0d6eaee2dee@gmail.com>
On Fri, 2016-08-26 at 09:56 -0700, Florian Fainelli wrote:
> On 08/24/2016 04:33 PM, Joe Perches wrote:
> >
> > Many email addresses in MAINTAINERS no longer work so many
> > sections in MAINTAINERS could likely be considered either
> > obsolete or unmaintained.
> >
> > Marking these sections appropriately or simply removing the
> > sections would make MAINTAINERS and get_maintainer.pl more
> > useful.
> >
> > These M: entries in MAINTAINERS haven't authored or had any
> > -by: signature entries in git log for the last 3 years.
> >
> > Some of these, like stable@kernel.org and trivial@kernel.org, are
> > obviously addresses that should not be deleted from MAINTAINERS,
> > but most of them are candidates for removal or update.
> >
> > The email addresses below are also bcc'd here to see what bounces.
> > The list of the bounces will be collected.
> >
> > Thoughts?
> >
> For:
> >
> > bcm-kernel-feedback-list@broadcom.com
> This mailing-list was recently added under the M: entry with commit
> 086f470481f5305ac52ce960e31a7d4441886e59 ("MAINTAINERS: Change L to M
> for Broadcom ARM/ARM64 SoC entries") (was L: before) since no external
> (to Broadcom) subscribers are allowed.
>
> Should we add a new tag for that kind of entry?
No, I think that's not necessary.
Exploders and aliases are just fine for M: entries.
The alias/exploder address can still get stale though.
Ideally, there would also be a specific actual person listed too.
btw: maybe these L: addresses could/should change
BROADCOM BRCMSTB GPIO DRIVER
M: Gregory Fong <gregory.0xf0@gmail.com>
L: bcm-kernel-feedback-list@broadcom.com
BROADCOM KONA GPIO DRIVER
M: Ray Jui <rjui@broadcom.com>
L: bcm-kernel-feedback-list@broadcom.com
BROADCOM STB NAND FLASH DRIVER
M: Brian Norris <computersforpeace@gmail.com>
M: Kamal Dasu <kdasu.kdev@gmail.com>
L: linux-mtd@lists.infradead.org
L: bcm-kernel-feedback-list@broadcom.com
SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI) Broadcom BRCMSTB DRIVER
M: Al Cooper <alcooperx@gmail.com>
L: linux-mmc@vger.kernel.org
L: bcm-kernel-feedback-list@broadcom.com
next prev parent reply other threads:[~2016-08-26 17:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 23:33 MAINTAINERS without commits in the last 3 years Joe Perches
[not found] ` <CA+i2_Ddvg9a0S23ywJtXQbLuq3JLJF9poH=n_G1+9uWWVPZwOg@mail.gmail.com>
2016-08-25 0:24 ` Joe Perches
[not found] ` <CAHrUA37xh-6GLkTAM75w8v550rR8n2Ayycjy9FNofv3K+=QoVQ@mail.gmail.com>
2016-08-25 2:09 ` Joe Perches
2016-08-25 3:26 ` Alexander Graf
2016-08-25 7:01 ` Ali Akcaagac
2016-08-25 7:29 ` Steve Twiss
2016-08-25 10:12 ` Mauro Carvalho Chehab
2016-08-25 16:12 ` David Carroll
2016-08-25 20:46 ` Steven French
2016-08-25 20:58 ` Greg KH
2016-08-26 0:33 ` Joe Perches
2016-08-26 12:59 ` Shuah Khan
2016-08-26 16:56 ` Florian Fainelli
2016-08-26 17:09 ` Joe Perches [this message]
2016-08-26 19:34 ` Jason Baron
2016-08-26 19:50 ` Joe Perches
2016-08-26 20:05 ` Borislav Petkov
2016-08-26 20:17 ` Luck, Tony
2016-09-01 12:58 ` Borislav Petkov
2016-09-01 16:02 ` Joe Perches
2016-09-02 5:26 ` Borislav Petkov
[not found] ` <CACwGpODqLAjQxgw=EdtWCKhFywy9btv9Ka6XG8YXbzKEBFPzEg@mail.gmail.com>
2016-08-28 2:40 ` Joe Perches
2016-08-30 15:19 ` Anders Larsen
2016-08-30 15:35 ` Joe Perches
2016-08-25 10:00 Tigran Aivazian
2016-08-25 10:09 ` Joe Perches
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=1472231363.4914.49.camel@perches.com \
--to=joe@perches.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).