From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: dt for 4.6 #2
Date: Wed, 02 Mar 2016 21:50:59 +0100 [thread overview]
Message-ID: <1634323.MskpPxvyZt@wuerfel> (raw)
In-Reply-To: <1456934722-7023-1-git-send-email-nicolas.ferre@atmel.com>
On Wednesday 02 March 2016 17:05:22 Nicolas Ferre wrote:
> A second batch of DT updates for 4.6. This time it is based on 4.5-rc3 as one
> of the patches fixes an node that was changed during 4.5-rc phase. As I saw
> that your "next/dt" branches are based on 4.5-rc3, I thought it wouldn't be a
> problem.
Right, thanks for checking.
> Overall a pretty simple series with mainly node addition for the latest SoC
> and its Xplained board.
> The tag doesn't embed Alexandre's previous DT Pull-Request for 4.6 that was
> based on 4.5-rc1. I verified though that it doesn't conflict with it during a
> merge.
Ok, that is good too. Pulled into next/dt now.
I see that your gpg key has expired last week, you may want to do something
about that, I think you can just update the date rather than creating a
new key.
Arnd
next prev parent reply other threads:[~2016-03-02 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 16:05 [GIT PULL] at91: dt for 4.6 #2 Nicolas Ferre
2016-03-02 20:50 ` Arnd Bergmann [this message]
2016-03-02 21:07 ` Alexandre Belloni
2016-03-02 21:27 ` Arnd Bergmann
2016-03-03 8:47 ` 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=1634323.MskpPxvyZt@wuerfel \
--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