From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] RealView device tree support
Date: Thu, 02 Oct 2014 16:46:39 +0200 [thread overview]
Message-ID: <3204791.dOjkWKTCre@wuerfel> (raw)
In-Reply-To: <CACRpkdbVtkme_CYrmF7ymsMGP3OO9mr_DPALRUeWGQh35-Uf=g@mail.gmail.com>
On Wednesday 01 October 2014 09:38:17 Linus Walleij wrote:
> A bit late maybe, so no biggie if this does not hit the merge
> window.
>
> However the dependent driver changes are already pending,
> and this is pretty isolated. Now the device tree support is
> split in two patches as requested.
You know I was really looking forward to this one, but I find
it hard to justify merging it now and not merging some of the
other parts I've started rejecting.
I've also twice been bitten now by 'just DT changes' that ended
up breaking the build, so I'd rather err on the side of being too
cautious now until the merge window.
Arnd
prev parent reply other threads:[~2014-10-02 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 7:38 [GIT PULL] RealView device tree support Linus Walleij
2014-10-02 14:46 ` 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=3204791.dOjkWKTCre@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