From: Joe Perches <joe@perches.com>
To: Michael Ellerman <mpe@ellerman.id.au>, Joel Stanley <joel@jms.id.au>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add powerpc drivers to the powerpc section
Date: Tue, 01 Mar 2016 19:33:02 -0800 [thread overview]
Message-ID: <1456889582.4436.43.camel@perches.com> (raw)
In-Reply-To: <1456888343.24490.8.camel@ellerman.id.au>
On Wed, 2016-03-02 at 14:12 +1100, Michael Ellerman wrote:
> On Wed, 2016-03-02 at 12:20 +1030, Joel Stanley wrote:
>
> >
> > On Wed, Mar 2, 2016 at 12:06 PM, Michael Ellerman wrote:
> >
> > >
> > > We'd like folks working on drivers for powerpc to also Cc linuxppc-dev,
> > > so we can be aware of what's going on in drivers and/or review the
> > > changes.
> > >
> > > So add patterns to the powerpc MAINTAINERS section to catch some of the
> > > drivers we're interested in.
> > There are a few more that would be good. '*opal*.c' catches these:
> >
> > ./drivers/i2c/busses/i2c-opal.c
> > ./drivers/rtc/rtc-opal.c
> > ./drivers/tty/hvc/hvc_opal.c
> Ah yep thanks, will add "N: opal".
N: and F: have different characteristics for get_maintainer.pl
>From MAINTAINERS:
scripts/get_maintainer.pl has different behavior for files that
match F: pattern and matches of N: patterns. By default,
get_maintainer will not look at git log history when an F: pattern
match occurs. When an N: match occurs, git log history is used
to also notify the people that have git commit signatures.
next prev parent reply other threads:[~2016-03-02 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 1:36 [PATCH] MAINTAINERS: Add powerpc drivers to the powerpc section Michael Ellerman
2016-03-02 1:50 ` Joel Stanley
2016-03-02 3:12 ` Michael Ellerman
2016-03-02 3:33 ` Joe Perches [this message]
2016-03-02 4:19 ` Mike & Meg
2016-04-11 12:35 ` Michael Ellerman
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=1456889582.4436.43.camel@perches.com \
--to=joe@perches.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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