From: Mike & Meg <mikenmeg@ellerman.id.au>
To: Joe Perches <joe@perches.com>, 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: Wed, 02 Mar 2016 15:19:21 +1100 [thread overview]
Message-ID: <1456892361.24490.10.camel@ellerman.id.au> (raw)
In-Reply-To: <1456889582.4436.43.camel@perches.com>
On Tue, 2016-03-01 at 19:33 -0800, Joe Perches wrote:
> 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.
Yeah I saw that.
What I want is to add linuxppc-dev to whatever it would have done previously.
ie. I don't want to hijack the patches from whoever would have got them.
And listing all the drivers explicitly would be a bit gross:
F: drivers/block/ps3disk.c
F: drivers/block/ps3vram.c
F: drivers/char/hw_random/powernv-rng.c
F: drivers/char/hw_random/pseries-rng.c
F: drivers/char/ipmi/ipmi_powernv.c
F: drivers/char/ps3flash.c
F: drivers/cpufreq/pmac32-cpufreq.c
F: drivers/cpufreq/pmac64-cpufreq.c
F: drivers/cpufreq/powernv-cpufreq.c
F: drivers/cpuidle/cpuidle-powernv.c
F: drivers/cpuidle/cpuidle-pseries.c
F: drivers/crypto/nx/nx-842-powernv.c
F: drivers/crypto/nx/nx-842-pseries.c
F: drivers/hwmon/ibmpowernv.c
F: drivers/i2c/busses/i2c-opal.c
F: drivers/i2c/busses/i2c-powermac.c
F: drivers/ide/pmac.c
F: drivers/leds/leds-powernv.c
F: drivers/media/rc/keymaps/rc-asus-ps3-100.c
F: drivers/mtd/devices/powernv_flash.c
F: drivers/net/ethernet/ti/cpmac.c
F: drivers/net/ethernet/toshiba/ps3_gelic_net.c
F: drivers/net/ethernet/toshiba/ps3_gelic_net.h
F: drivers/net/ethernet/toshiba/ps3_gelic_wireless.c
F: drivers/net/ethernet/toshiba/ps3_gelic_wireless.h
F: drivers/ps3/ps3av.c
F: drivers/ps3/ps3av_cmd.c
F: drivers/ps3/ps3-lpm.c
F: drivers/ps3/ps3stor_lib.c
F: drivers/ps3/ps3-sys-manager.c
F: drivers/ps3/ps3-vuart.c
F: drivers/rtc/rtc-opal.c
F: drivers/rtc/rtc-ps3.c
F: drivers/scsi/ps3rom.c
F: drivers/tty/hvc/hvc_opal.c
F: drivers/tty/serial/pmac_zilog.c
F: drivers/tty/serial/pmac_zilog.h
F: drivers/usb/host/ehci-ps3.c
F: drivers/usb/host/ohci-ps3.c
F: drivers/video/fbdev/ps3fb.c
F: sound/ppc/pmac.c
F: sound/ppc/pmac.h
F: sound/ppc/powermac.c
F: sound/ppc/snd_ps3.c
F: sound/ppc/snd_ps3.h
F: sound/ppc/snd_ps3_reg.h
cheers
next prev parent reply other threads:[~2016-03-02 4:19 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
2016-03-02 4:19 ` Mike & Meg [this message]
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=1456892361.24490.10.camel@ellerman.id.au \
--to=mikenmeg@ellerman.id.au \
--cc=joe@perches.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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