From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: soc for 3.18 #2
Date: Fri, 26 Sep 2014 00:17:01 +0200 [thread overview]
Message-ID: <201409260017.01469.arnd@arndb.de> (raw)
In-Reply-To: <1411391733-28891-1-git-send-email-nicolas.ferre@atmel.com>
On Monday 22 September 2014, Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> This is the second SoC pull-request for AT91 and it's dedicated to the addition
> of our new SAMA5D4: C-A5+neon+L2CC+vdec (in sort). The AT91 SoC support is now
> pretty simple in relation with the enhancements done recently.
> The patches go on top of the previous tag at91-soc and has no dependency.
>
> The merge with other AT91 branches can lead to little conflicts that I resolved
> for you in the at91-3.18-resolved2 branch that you can take as an example.
>
> Thanks, best regards,
>
> The following changes since commit 5db722eeba0051c68e638114f6720e715b03cd2c:
>
> ARM: at91: Remove the support for the RSI EWS board (2014-09-19 13:13:23 +0200)
>
> are available in the git repository at:
>
> git://github.com/at91linux/linux-at91.git tags/at91-soc2
>
> for you to fetch changes up to 02037a9719fa89b7e5dc25cb22afc06c4eae406e:
>
> ARM: at91: document Atmel SMART compatibles (2014-09-22 14:42:40 +0200)
>
> ----------------------------------------------------------------
> Second SoC batch for 3.18:
> - introduction of the new SAMA5D4 SoC and associated Evaluation Kit
> - low level soc detection and early printk code
> - taking advantage of this, documentation of all AT91 SoC DT strings
Pulled into next/soc, thanks!
Arnd
next prev parent reply other threads:[~2014-09-25 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 13:15 [GIT PULL] at91: soc for 3.18 #2 Nicolas Ferre
2014-09-25 22:17 ` Arnd Bergmann [this message]
2014-09-26 10:50 ` Arnd Bergmann
2014-09-26 13:02 ` Alexandre Belloni
2014-09-26 14:47 ` Nicolas Ferre
2014-09-26 18:55 ` Arnd Bergmann
2014-09-29 8:52 ` Nicolas Ferre
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=201409260017.01469.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 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).