From: Arnd Bergmann <arnd@arndb.de>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Olof Johansson <olof@lixom.net>,
arm@kernel.org, Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ARM: at91: dt for 4.8 #3
Date: Fri, 15 Jul 2016 23:05:42 +0200 [thread overview]
Message-ID: <2396021.xcmCDpBAY8@wuerfel> (raw)
In-Reply-To: <20160715205826.GA31997@piout.net>
On Friday, July 15, 2016 10:58:26 PM CEST Alexandre Belloni wrote:
> DT Changes for 4.8 #3:
> - Lot of fixes for dtc warnings
> - Separate dtb compilation for ARMv4 and ARMv5
Great timing, I was just looking for things to merge before the end
of the week, so I pulled it into next/dt and pushed it out.
Thanks for addressing both issues!
Arnd
prev parent reply other threads:[~2016-07-15 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 20:58 [GIT PULL] ARM: at91: dt for 4.8 #3 Alexandre Belloni
2016-07-15 21:05 ` Arnd Bergmann [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=2396021.xcmCDpBAY8@wuerfel \
--to=arnd@arndb.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
/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