From: Arnd Bergmann <arnd@arndb.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>,
arm@kernel.org, Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: Re: [GIT PULL 1/3] ARM: exynos: Soc/mach for v4.10
Date: Fri, 02 Dec 2016 22:52:57 +0100 [thread overview]
Message-ID: <57568492.9hbg5JCdec@wuerfel> (raw)
In-Reply-To: <20161201183404.GA2134@kozik-lap>
On Thursday, December 1, 2016 8:34:04 PM CET Krzysztof Kozlowski wrote:
> On Thu, Nov 24, 2016 at 08:08:27AM +0200, Krzysztof Kozlowski wrote:
> > Hi,
> >
> > This contains previous dts branch because SCU node in dts is needed
> > prior to removing it from mach code.
> >
> > Below you will find full pull request and one stripped from dependency.
> >
>
> Hi Arnd, Kevin and Olof,
>
> What about this pull from the set?
>
Sorry, I initially deferred it and then didn't get back to it.
The dependency on the .dts changes made me a bit nervous about
taking it, mostly because the changelog fails to explain the
exact dependencies.
This breaks compatibility with existing .dtb files, right?
What I'd like to see here is an explanation about:
- what the upside of breaking compatibility is
- what exactly stops working with an old dtb
- why we don't keep a fallback for handling old dtb files
It would also be helpful to have a separate pull request for
the commits require the new dtb, and the stuff that is unrelated.
Arnd
next prev parent reply other threads:[~2016-12-02 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 6:08 [GIT PULL 0/3] ARM: exynos: Second round for v4.10 Krzysztof Kozlowski
2016-11-24 6:08 ` [GIT PULL 1/3] ARM: exynos: Soc/mach " Krzysztof Kozlowski
2016-12-01 18:34 ` Krzysztof Kozlowski
2016-12-02 21:52 ` Arnd Bergmann [this message]
2016-12-03 17:03 ` Krzysztof Kozlowski
2016-12-08 15:28 ` Pankaj Dubey
2016-12-08 18:25 ` Olof Johansson
2016-12-08 18:46 ` Krzysztof Kozlowski
2016-11-24 6:08 ` [GIT PULL 2/3] ARM: dts: exynos: DT for v4.10, second round Krzysztof Kozlowski
2016-11-30 21:39 ` Arnd Bergmann
2016-11-24 6:08 ` [GIT PULL 3/3] arm64: " Krzysztof Kozlowski
2016-11-30 21:47 ` Arnd Bergmann
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=57568492.9hbg5JCdec@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/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).