From: Michael Ellerman <mpe@ellerman.id.au>
To: 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 14:12:23 +1100 [thread overview]
Message-ID: <1456888343.24490.8.camel@ellerman.id.au> (raw)
In-Reply-To: <CACPK8Xe+vxJe-ArTP7ZU4gKjJtZwviT0t9h7kS1R1WvW6E-msA@mail.gmail.com>
On Wed, 2016-03-02 at 12:20 +1030, Joel Stanley wrote:
> On Wed, Mar 2, 2016 at 12:06 PM, Michael Ellerman <mpe@ellerman.id.au> 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".
> 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
next prev parent reply other threads:[~2016-03-02 3:12 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 [this message]
2016-03-02 3:33 ` Joe Perches
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=1456888343.24490.8.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.