linux-kernel - Re: [PATCH] get_maintainer: Don't fallback to git by default

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]

Date:	Tue, 27 Oct 2015 16:37:31 -0700
From:	Joe Perches <joe@...ches.com>
To:	Wolfram Sang <wsa@...-dreams.de>
Cc:	Lee Jones <lee.jones@...aro.org>, Theodore Ts'o <tytso@....edu>,
	Javier Martinez Canillas <javier@....samsung.com>,
	Laura Abbott <labbott@...hat.com>,
	linux-kernel@...r.kernel.org, linux-kernel-owner@...r.kernel.org
Subject: Re: [PATCH] get_maintainer: Don't fallback to git by default

On Wed, 2015-10-28 at 00:25 +0100, Wolfram Sang wrote:
> > Another option would be to add another pattern to the
> > I2C section that matches all subdirectories of drivers/i2c/:
> > ---
> >  MAINTAINERS | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index fb7d2e4..c670e1f 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -5104,6 +5104,7 @@ S:	Maintained
> >  F:	Documentation/devicetree/bindings/i2c/
> >  F:	Documentation/i2c/
> >  F:	drivers/i2c/
> > +F:	drivers/i2c/*/
> 
> Hmm, what would be the drawback of extending the meaning of
> 'drivers/i2c/' to include 'drivers/i2c/*/'? To be honest, I assumed it
> works this way already and I'd think I am not alone with that
> assumption.

Some top level directories contain other subsystems.

A maintainer of something like arch/arm doesn't generally
want to be the maintainer of arch/arm/mach-<foo>

You _want_ a wider number of reviewers for patches to any
of those unmaintained subsystems.

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