From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Integrator cleanups and DTS
Date: Wed, 14 Sep 2016 17:56:47 +0200 [thread overview]
Message-ID: <3954604.JGQyd7kqGb@wuerfel> (raw)
In-Reply-To: <CACRpkdYBB0rw3uQZnmpsuc_=mf5Ra-HmbRfdm6aT0kn9rn41Lg@mail.gmail.com>
On Wednesday, August 31, 2016 9:44:55 AM CEST Linus Walleij wrote:
> Hi ARM SoC people,
>
> this is a request to pull a combined cleanup and DTS changes batch
> for the Integrators.
>
> Since I have commits such as "move CLCD display to DTS" that is
> a single functional change deleting stuff from the boardfile and adding
> the same to the DTS, it is a combination of DTS and boardfile patches.
> All with the goal to cut down on boardfile code and move to device tree.
>
> The changes require the corresponding changes from the video/fbdev
> and clk subsystems to come in, but these are orthogonal and depend
> solely on the DTS things coming in place. As the DTS repository is
> "kind of external" I am deliverately relaxed about synchronizing changes
> here and just optimistically assume they will come in during the merge
> window and start working.
>
> There are no compile-time dependencies on fbdev or clk, just runtime,
> with the DT changes. This cleanup can be merged totally orthogonally,
> and when ARM SoC, fbdev and clk are all merged in the merge window,
> the result will compile and boot nicely.
>
> I don't expect any conflicting changes to the Integrator in this merge
> window, neither to board files nor DTS.
>
I've put this into next/late since it's not just dts changes. I considered
putting it into next/cleanup, but then again it's also not just cleanups.
Given the dependency on the fbdev and clk trees, next/late seems appropriate
anyway, thanks!
Arnd
prev parent reply other threads:[~2016-09-14 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 7:44 [GIT PULL] Integrator cleanups and DTS Linus Walleij
2016-09-14 15:56 ` 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=3954604.JGQyd7kqGb@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