From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL V2] ARM: mvebu: dt changes for v3.15 (incr. pull #3)
Date: Mon, 17 Mar 2014 11:11:30 +0100 [thread overview]
Message-ID: <201403171111.30596.arnd@arndb.de> (raw)
In-Reply-To: <20140304025559.GY1872@titan.lakedaemon.net>
On Tuesday 04 March 2014, Jason Cooper wrote:
> V2: removed the dove PMU interrupt node (er, undid the re-addition of
> the node. ie: let the revert stand). So, commit id's for this pull
> only are changed. No previous pulls or tags affected. Confirmed the
> change with a diff between the old branch and the new branch. And did a
> run of building dtbs. No problems. Sorry for the confusion.
>
> Russell just raised a very valid point today regarding the overall
> design of an eventual PMU driver that would cover several tasks we
> hadn't considered with the original binding. Better to pull it now than
> have to support it indefinitely. Revert of the driver in the works.
>
> --- original text ---
>
> Here's another rather large round of DT changes for mvebu. It's all
> summed up below and has been in -next for a while now.
>
> This is an incremental pull from tags/mvebu-dt-3.15-2 in the mvebu/dt
> branch up to tags/mvebu-dt-3.15-3.
>
Pulled into next/dt now, along with the #4 and #5. I got a trivial
merge conflict against the dts Makefile change from mach-qcom and
noticed that splitting up the dtb section into per-soc breaks
alphabetical ordering, which I changed in the merge by moving
it down to the end of the list.
Arnd
next prev parent reply other threads:[~2014-03-17 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 5:25 [GIT PULL] ARM: mvebu: dt changes for v3.15 (incr. pull #3) Jason Cooper
2014-03-03 22:26 ` Jason Cooper
2014-03-04 2:55 ` [GIT PULL V2] " Jason Cooper
2014-03-17 10:11 ` Arnd Bergmann [this message]
2014-03-17 14:23 ` Jason Cooper
2014-03-18 12:55 ` Arnd Bergmann
2014-03-18 13:01 ` Jason Cooper
2014-03-17 19:35 ` 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=201403171111.30596.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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