linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Add patterns for DTS files for AT91
Date: Wed, 16 Oct 2013 16:01:13 +0200	[thread overview]
Message-ID: <525E9C29.7010301@atmel.com> (raw)
In-Reply-To: <1381921447-21811-1-git-send-email-broonie@kernel.org>

On 16/10/2013 13:04, Mark Brown :
> From: Mark Brown <broonie@linaro.org>
>
> Help ensure updates to the DTS files for AT91 machines and devices get
> sent to the maintainers by adding patterns to the MAINTAINERS entry for
> the architecture.
>
> Signed-off-by: Mark Brown <broonie@linaro.org>
> ---
>   MAINTAINERS | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d5714d0..c610fb8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -777,6 +777,8 @@ W:	http://maxim.org.za/at91_26.html
>   W:	http://www.linux4sam.org
>   S:	Supported
>   F:	arch/arm/mach-at91/
> +F:	arch/arm/boot/dts/at91*.dts
> +F:	arch/arm/boot/dts/at91*.dtsi

Unfortunately, we added some more strings for our new C-A5 product 
family. I tried to be more generic possible without messing with other 
product names. So what about adding these lines?

+F:	arch/arm/boot/dts/sama*.dts
+F:	arch/arm/boot/dts/sama*.dtsi

If it is okay with you, I can add them directly in your patch when 
taking it in my tree, do not bother.


>   ARM/CALXEDA HIGHBANK ARCHITECTURE
>   M:	Rob Herring <rob.herring@calxeda.com>

Thanks, bye,
-- 
Nicolas Ferre

  reply	other threads:[~2013-10-16 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 11:04 [PATCH] MAINTAINERS: Add patterns for DTS files for AT91 Mark Brown
2013-10-16 14:01 ` Nicolas Ferre [this message]
2013-10-16 14:16   ` Mark Brown

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=525E9C29.7010301@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).