From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Update entry for omap related .dts files to cover new SoCs
Date: Mon, 10 Nov 2014 12:30:17 -0800 [thread overview]
Message-ID: <20141110203017.GT31454@atomide.com> (raw)
In-Reply-To: <1413901462-32181-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [141021 07:25]:
> DRA7(including AM5x) and AM47x series are handled under OMAP umbrella.
> These SoC support and dts have been added since 3.14 kernel and Pull
> requests for these have come in from OMAP till date.
>
> So just ensure that get_maintainers can pick up this list as well.
Applying this into omap-for-v3.18/fixes as we've seen some
patches not copied to linux-omap list.
Regards,
Tony
> Cc: Benoît Cousson <bcousson@baylibre.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: linux-omap@vger.kernel.org
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a20df9b..e205bd2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6585,6 +6585,9 @@ L: devicetree@vger.kernel.org
> S: Maintained
> F: arch/arm/boot/dts/*omap*
> F: arch/arm/boot/dts/*am3*
> +F: arch/arm/boot/dts/*am4*
> +F: arch/arm/boot/dts/*am5*
> +F: arch/arm/boot/dts/*dra7*
>
> OMAP CLOCK FRAMEWORK SUPPORT
> M: Paul Walmsley <paul@pwsan.com>
> --
> 1.7.9.5
>
prev parent reply other threads:[~2014-11-10 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 14:24 [PATCH] MAINTAINERS: Update entry for omap related .dts files to cover new SoCs Nishanth Menon
2014-10-21 14:26 ` Benoit Cousson
2014-11-10 20:30 ` Tony Lindgren [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=20141110203017.GT31454@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).