linux-kernel - Re: MAINTAINERS without commits in the last 3 years

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: <1472231363.4914.49.camel@perches.com>
Date:   Fri, 26 Aug 2016 10:09:23 -0700
From:   Joe Perches <joe@...ches.com>
To:     Florian Fainelli <f.fainelli@...il.com>,
        LKML <linux-kernel@...r.kernel.org>
Cc:     bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>
Subject: Re: MAINTAINERS without commits in the last 3 years

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@...nel.org and trivial@...nel.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@...adcom.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@...il.com>
L:	bcm-kernel-feedback-list@...adcom.com

BROADCOM KONA GPIO DRIVER
M:	Ray Jui <rjui@...adcom.com>
L:	bcm-kernel-feedback-list@...adcom.com

BROADCOM STB NAND FLASH DRIVER
M:	Brian Norris <computersforpeace@...il.com>
M:	Kamal Dasu <kdasu.kdev@...il.com>
L:	linux-mtd@...ts.infradead.org
L:	bcm-kernel-feedback-list@...adcom.com

SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI) Broadcom BRCMSTB DRIVER
M:	Al Cooper <alcooperx@...il.com>
L:	linux-mmc@...r.kernel.org
L:	bcm-kernel-feedback-list@...adcom.com