From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: DT changes for 3.10 #3
Date: Tue, 9 Apr 2013 12:49:38 +0200 [thread overview]
Message-ID: <201304091249.38903.arnd@arndb.de> (raw)
In-Reply-To: <1365094799-16940-1-git-send-email-nicolas.ferre@atmel.com>
On Thursday 04 April 2013, Nicolas Ferre wrote:
> Here is the refreshed pull-request for AT91 that is dedicated to Device Tree
> modifications. It is stacked on the material that you already have
> for 3.10 in your arm-soc/at91/dt branch.
> Following our discussion with Arnd, I added the non-urgent patches that I
> already proposed too late for 3.9. I also included the moving of macb node
> and kept the original patch.
>
> As Olof asked, I renamed the Aria board dts file: at91-ariag25.dts and placed
> it in the Makefile. I also took the advantage of this delay to stack two more
> DT related patches.
>
Pulled into next/dt, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Olof Johansson <olof@lixom.net>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dgilbert@interlog.com
Subject: Re: [GIT PULL] at91: DT changes for 3.10 #3
Date: Tue, 9 Apr 2013 12:49:38 +0200 [thread overview]
Message-ID: <201304091249.38903.arnd@arndb.de> (raw)
In-Reply-To: <1365094799-16940-1-git-send-email-nicolas.ferre@atmel.com>
On Thursday 04 April 2013, Nicolas Ferre wrote:
> Here is the refreshed pull-request for AT91 that is dedicated to Device Tree
> modifications. It is stacked on the material that you already have
> for 3.10 in your arm-soc/at91/dt branch.
> Following our discussion with Arnd, I added the non-urgent patches that I
> already proposed too late for 3.9. I also included the moving of macb node
> and kept the original patch.
>
> As Olof asked, I renamed the Aria board dts file: at91-ariag25.dts and placed
> it in the Makefile. I also took the advantage of this delay to stack two more
> DT related patches.
>
Pulled into next/dt, thanks!
Arnd
next prev parent reply other threads:[~2013-04-09 10:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 14:59 [GIT PULL] at91: DT changes for 3.10 #2 Nicolas Ferre
2013-03-29 14:59 ` Nicolas Ferre
2013-04-02 18:49 ` Olof Johansson
2013-04-02 18:49 ` Olof Johansson
2013-04-03 7:45 ` Nicolas Ferre
2013-04-03 7:45 ` Nicolas Ferre
2013-04-04 9:37 ` Nicolas Ferre
2013-04-04 9:37 ` Nicolas Ferre
2013-04-04 17:19 ` Olof Johansson
2013-04-04 17:19 ` Olof Johansson
2013-04-08 11:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 11:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-04 15:42 ` [PATCH v3] ARM: at91: add Acme Systems Aria G25 board Nicolas Ferre
2013-04-04 15:42 ` Nicolas Ferre
2013-04-04 17:03 ` Douglas Gilbert
2013-04-04 17:03 ` Douglas Gilbert
2013-04-18 9:01 ` Nicolas Ferre
2013-04-18 9:01 ` Nicolas Ferre
2013-04-18 10:13 ` Nicolas Ferre
2013-04-18 10:13 ` Nicolas Ferre
2013-04-04 16:59 ` [GIT PULL] at91: DT changes for 3.10 #3 Nicolas Ferre
2013-04-04 16:59 ` Nicolas Ferre
2013-04-09 8:17 ` Nicolas Ferre
2013-04-09 8:17 ` Nicolas Ferre
2013-04-09 9:47 ` Arnd Bergmann
2013-04-09 9:47 ` Arnd Bergmann
2013-04-09 10:49 ` Arnd Bergmann [this message]
2013-04-09 10:49 ` Arnd Bergmann
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=201304091249.38903.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.