From: Mike Turquette <mturquette@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: arm@kernel.org, "Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Mark Brown" <broonie@kernel.org>,
"Grant Likely" <grant.likely@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
kernel@pengutronix.de
Subject: Re: [PATCH v2] MAINTAINERS: take maintainership for Energy Micro efm32 SoCs
Date: Sun, 22 Dec 2013 12:54:14 -0800 [thread overview]
Message-ID: <20131222205414.22761.9778@quantum> (raw)
In-Reply-To: <1387570919-13627-1-git-send-email-u.kleine-koenig@pengutronix.de>
Quoting Uwe Kleine-König (2013-12-20 12:21:59)
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Acked-by: Mark Brown <broonie@linaro.org>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
>
> On Fri, Dec 20, 2013 at 11:55:30PM +0400, Alexander Shiyan wrote:
> > [...]
> > > +F: arch/arm/boot/dts/efm32*
> > > +F: arch/arm/configs/efm32_defconfig
> > > +F: arch/arm/include/debug/efm32.S
> > > +F: arch/arm/mach-efm32/
> > > +F: drivers/clk/clk-efm32gg.c
> > > +F: drivers/clocksource/time-efm32.c
> > > +F: drivers/spi/spi-efm32.c
> > > +F: drivers/tty/serial/efm32-uart.c
> > > +F: include/dt-bindings/clock/efm32-cmu.h
> > > +F: include/linux/platform_data/efm32-*
> >
> > Maybe "N" keyword with "efm32" is better here?
> ah, didn't know about that. Nice.
>
> So the changes since v1 are:
> - use N: efm32
> - add acks from Greg and Mark
> I assume it's ok to keep them for v2 assuming they mean them being OK with
> me maintaining the efm32 stuff and not the way to express that in
> MAINTAINERS.
Ack for the clock driver.
Mike
>
> Thanks
> Uwe
>
> MAINTAINERS | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 95648eb..6ea1fb2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -867,6 +867,12 @@ S: Maintained
> F: arch/arm/mach-ebsa110/
> F: drivers/net/ethernet/amd/am79c961a.*
>
> +ARM/ENERGY MICRO (SILICON LABS) EFM32 SUPPORT
> +M: Uwe Kleine-König <kernel@pengutronix.de>
> +L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> +S: Maintained
> +N: efm32
> +
> ARM/EZX SMARTPHONES (A780, A910, A1200, E680, ROKR E2 and ROKR E6)
> M: Daniel Ribeiro <drwyrm@gmail.com>
> M: Stefan Schmidt <stefan@openezx.org>
> --
> 1.8.5.1
>
prev parent reply other threads:[~2013-12-22 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 19:39 [PATCH] MAINTAINERS: take maintainership for Energy Micro efm32 SoCs Uwe Kleine-König
2013-12-20 19:51 ` Greg Kroah-Hartman
2013-12-20 19:51 ` Mark Brown
2013-12-20 19:55 ` Alexander Shiyan
2013-12-20 20:21 ` [PATCH v2] " Uwe Kleine-König
2013-12-21 4:29 ` MAINTAINERS: Describe differences between F: and N: patterns Joe Perches
2013-12-22 20:04 ` [PATCH v2] MAINTAINERS: take maintainership for Energy Micro efm32 SoCs Olof Johansson
2013-12-22 20:54 ` Mike Turquette [this message]
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=20131222205414.22761.9778@quantum \
--to=mturquette@linaro.org \
--cc=arm@kernel.org \
--cc=broonie@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.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