From: Michael Ellerman <mpe@ellerman.id.au> Date: 2016-03-02 01:37:01
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.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
MAINTAINERS | 12 ++++++++++++
1 file changed, 12 insertions(+)
If I've missed some let me know.
From: Joel Stanley <joel@jms.id.au> Date: 2016-03-02 01:50:36
On Wed, Mar 2, 2016 at 12:06 PM, Michael Ellerman [off-list ref] 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
and '*powernv*.c' gets these (some a duplicates with what you have):
./drivers/leds/leds-powernv.c
./drivers/cpufreq/powernv-cpufreq.c
./drivers/mtd/devices/powernv_flash.c
./drivers/cpuidle/cpuidle-powernv.c
./drivers/char/hw_random/powernv-rng.c
./drivers/char/ipmi/ipmi_powernv.c
./drivers/hwmon/ibmpowernv.c
./drivers/crypto/nx/nx-842-powernv.c
Cheers,
Joel
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2016-03-02 03:12:26
On Wed, 2016-03-02 at 12:20 +1030, Joel Stanley wrote:
On Wed, Mar 2, 2016 at 12:06 PM, Michael Ellerman [off-list ref] wrote:
quoted
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".
and '*powernv*.c' gets these (some a duplicates with what you have):
./drivers/leds/leds-powernv.c
./drivers/cpufreq/powernv-cpufreq.c
./drivers/mtd/devices/powernv_flash.c
./drivers/cpuidle/cpuidle-powernv.c
./drivers/char/hw_random/powernv-rng.c
./drivers/char/ipmi/ipmi_powernv.c
./drivers/hwmon/ibmpowernv.c
./drivers/crypto/nx/nx-842-powernv.c
They should all be covered by "N: powernv" I think:
$ for f in ./drivers/leds/leds-powernv.c ./drivers/cpufreq/powernv-cpufreq.c ./drivers/mtd/devices/powernv_flash.c ./drivers/cpuidle/cpuidle-powernv.c ./drivers/char/hw_random/powernv-rng.c
./drivers/char/ipmi/ipmi_powernv.c ./drivers/hwmon/ibmpowernv.c ./drivers/crypto/nx/nx-842-powernv.c; do echo -en "$f\t"; ./scripts/get_maintainer.pl -f $f | grep linuxppc-dev; done
./drivers/leds/leds-powernv.c linuxppc-dev@lists.ozlabs.org
./drivers/cpufreq/powernv-cpufreq.c linuxppc-dev@lists.ozlabs.org
./drivers/mtd/devices/powernv_flash.c linuxppc-dev@lists.ozlabs.org
./drivers/cpuidle/cpuidle-powernv.c linuxppc-dev@lists.ozlabs.org
./drivers/char/hw_random/powernv-rng.c linuxppc-dev@lists.ozlabs.org
./drivers/char/ipmi/ipmi_powernv.c linuxppc-dev@lists.ozlabs.org
./drivers/hwmon/ibmpowernv.c linuxppc-dev@lists.ozlabs.org
./drivers/crypto/nx/nx-842-powernv.c linuxppc-dev@lists.ozlabs.org
cheers
From: Joe Perches <joe@perches.com> Date: 2016-03-02 03:33:09
On Wed, 2016-03-02 at 14:12 +1100, Michael Ellerman wrote:
On Wed, 2016-03-02 at 12:20 +1030, Joel Stanley wrote:
quoted
On Wed, Mar 2, 2016 at 12:06 PM, Michael Ellerman wrote:
quoted
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.
From: Mike & Meg <hidden> Date: 2016-03-02 04:19:24
On Tue, 2016-03-01 at 19:33 -0800, Joe Perches wrote:
On Wed, 2016-03-02 at 14:12 +1100, Michael Ellerman wrote:
quoted
On Wed, 2016-03-02 at 12:20 +1030, Joel Stanley wrote:
quoted
On Wed, Mar 2, 2016 at 12:06 PM, Michael Ellerman wrote:
quoted
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
quoted
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
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2016-04-11 12:35:21
On Wed, 2016-02-03 at 01:36:56 UTC, 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.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>