From: Joe Perches <joe@perches.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Lee Jones <lee.jones@linaro.org>, "Theodore Ts'o" <tytso@mit.edu>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Laura Abbott <labbott@redhat.com>,
linux-kernel@vger.kernel.org, linux-kernel-owner@vger.kernel.org
Subject: Re: [PATCH] get_maintainer: Don't fallback to git by default
Date: Tue, 27 Oct 2015 16:37:31 -0700 [thread overview]
Message-ID: <1445989051.2757.65.camel@perches.com> (raw)
In-Reply-To: <20151027232526.GA1572@katana>
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.
next prev parent reply other threads:[~2015-10-27 23:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 22:11 Javier Martinez Canillas
2015-10-26 23:00 ` Laura Abbott
2015-10-27 0:08 ` Javier Martinez Canillas
2015-10-27 2:47 ` Theodore Ts'o
2015-10-27 4:57 ` joe
2015-10-27 5:03 ` Laura Abbott
2015-10-27 8:21 ` Lee Jones
2015-10-27 9:24 ` Wolfram Sang
2015-10-27 10:10 ` Lee Jones
2015-10-27 10:29 ` Wolfram Sang
2015-10-27 17:49 ` Joe Perches
2015-10-27 18:21 ` Joe Perches
2015-10-27 23:25 ` Wolfram Sang
2015-10-27 23:37 ` Joe Perches [this message]
2015-10-28 0:05 ` Wolfram Sang
2015-10-28 0:14 ` Joe Perches
2015-10-28 8:50 ` Lee Jones
2015-10-27 17:53 ` Joe Perches
2015-10-27 18:09 ` Lee Jones
2015-10-27 19:24 ` Javier Martinez Canillas
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=1445989051.2757.65.camel@perches.com \
--to=joe@perches.com \
--cc=javier@osg.samsung.com \
--cc=labbott@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wsa@the-dreams.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
Powered by JetHome