From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] RaspberryPi Device Tree changes due for v4.2
Date: Fri, 15 May 2015 17:25:55 +0200 [thread overview]
Message-ID: <12863895.JAAhhHt9YQ@wuerfel> (raw)
In-Reply-To: <20150514092330.GE22418@x1>
On Thursday 14 May 2015 10:23:30 Lee Jones wrote:
> RaspberryPi Device Tree changes due for v4.2
Pulled into next/dt, since I'm already at it.
Could you send these to Florian in the future so he can forward
them to us along with the other mach-bcm changes?
Arnd
next prev parent reply other threads:[~2015-05-15 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 9:23 [GIT PULL] RaspberryPi Device Tree changes due for v4.2 Lee Jones
2015-05-15 15:25 ` Arnd Bergmann [this message]
2015-05-19 12:53 ` Lee Jones
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=12863895.JAAhhHt9YQ@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