From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: Last DT changes for v3.18
Date: Thu, 02 Oct 2014 17:20:53 +0200 [thread overview]
Message-ID: <1850328.rMhfjqiuR3@wuerfel> (raw)
In-Reply-To: <20141002135926.GC27230@titan.lakedaemon.net>
On Thursday 02 October 2014 09:59:26 Jason Cooper wrote:
>
> I know this is way late, but the changes a fairly small, and have been
> in linux-next for at least 9 of Stephen's 'next-YYYYMMDD' tags.
> Hopefully the merge window opening a week late will make it possible for
> you guys to take this.
>
> This is an incremental pull request from tags/mvebu-dt-3.18 up to
> tags/mvebu-dt-3.18-2 on the mvebu/dt branch.
The one patch is a bug fix, so it's exempt from the deadline, the other
one is obviously harmless, so I'm pulling it into next/dt.
Regarding the DT change: Seriously? They made the same mistake
*AGAIN*? I hope that whoever at Marvell decided to change the
register location for a shipping product in a boot loader update
will lose their commit access.
Arnd
next prev parent reply other threads:[~2014-10-02 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 13:59 [GIT PULL] ARM: mvebu: Last DT changes for v3.18 Jason Cooper
2014-10-02 15:20 ` Arnd Bergmann [this message]
2014-10-02 20:50 ` Jason Cooper
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=1850328.rMhfjqiuR3@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;
as well as URLs for NNTP newsgroup(s).