public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
	"Mike Turquette" <mturquette@linaro.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Mark Brown" <broonie@kernel.org>,
	"Daniel Lezcano" <daniel.lezcano@linaro.org>,
	arm@kernel.org, kernel@pengutronix.de,
	"Grant Likely" <grant.likely@linaro.org>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH] MAINTAINERS: take maintainership for Energy Micro efm32 SoCs
Date: Fri, 20 Dec 2013 23:55:30 +0400	[thread overview]
Message-ID: <1387569330.616105313@f421.i.mail.ru> (raw)
In-Reply-To: <1387568343-8754-1-git-send-email-u.kleine-koenig@pengutronix.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1239 bytes --]

> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
...
> I think this can best go in via armsoc, but needs acks for clk, clocksource,
> spi and tty/serial.
...
>  MAINTAINERS | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 95648eb..28c69a6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -867,6 +867,21 @@ 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
> +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?

---
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  parent reply	other threads:[~2013-12-20 19:56 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 [this message]
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

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=1387569330.616105313@f421.i.mail.ru \
    --to=shc_work@mail.ru \
    --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=mturquette@linaro.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