Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: krzk@kernel.org (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round
Date: Tue, 14 Feb 2017 18:52:29 +0200	[thread overview]
Message-ID: <20170214165229.y3udmy7w5gm27tys@kozik-lap> (raw)
In-Reply-To: <8a236294-a561-a857-403e-3a3a794b31f3@samsung.com>

On Fri, Feb 10, 2017 at 12:30:48PM +0100, Sylwester Nawrocki wrote:
> On 02/09/2017 07:56 PM, Krzysztof Kozlowski wrote:
> > On Thu, Feb 09, 2017 at 04:19:57PM +0100, Arnd Bergmann wrote:
> >> On Thursday, February 2, 2017 8:30:08 PM CET Krzysztof Kozlowski wrote:
> >>>  arch/arm64/boot/dts/exynos/exynos5433-tm2.dts      |  34 +++
> >>>  arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts     |  34 +++
> >>>  arch/arm64/boot/dts/exynos/exynos7-espresso.dts    |  49 +++-
> >>>  arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi    | 302 +++++++++++----------
> >>>  arch/arm64/boot/dts/exynos/exynos7.dtsi            |  34 +++
> >>>  drivers/clk/samsung/clk-exynos5433.c               |   8 +-
> >>>  include/dt-bindings/clock/exynos5433.h             |   5 +-
> >>>  include/dt-bindings/pinctrl/samsung.h              |   8 +
> >>>
> >> It seems a drivers/clk change slipped in there in addition to the header changes.
> >> We are trying to keep the next/dt branches free of driver changes, are you
> >> able to rework the branch without this?
> >
> > +Cc Sylwester,
> > 
> > This came from clk tree from Sylwester. It contains two changes in
> > clocks:
> > 1. Mew clock ID - we need only the header but Sylwester provided also
> >    the source file change,
> 
> That's a one patch made so there is no runtime regression.  If we stick
> to the next/dt branches being clean of driver changes I'm afraid we need
> to be prepared for the bisection breaks.
> 
> > 2. Update of frequency (used in DTS as assigned clock rate) - this
> >    is strictly source file change and we need it.
> > 
> > Overall, rework would not be trivial and it would involve Sylwester.
> > I think it is better to stay with this as is. I will remember the policy
> > for future dependencies.
> 
> The clk changes are already pulled into clk tree, we would get conflicts
> with commits that are already in the clock tree if the branch is reworked
> now.  This might not be a big issue but bisection would be broken for sure.
> 
> I'll also try to keep in future include/dt-bindings changes separate.

Arnd,

Any further comments? Are you going to pull it in?

Best regards,
Krzysztof

  reply	other threads:[~2017-02-14 16:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 18:30 [GIT PULL 0/4] ARM: exynos: Third (last) round for v4.11 Krzysztof Kozlowski
2017-02-02 18:30 ` [GIT PULL 1/4] soc: samsung: pm_domains " Krzysztof Kozlowski
2017-02-07 16:21   ` Arnd Bergmann
2017-02-02 18:30 ` [GIT PULL 2/4] soc: samsung: pmu for v4.11, third round Krzysztof Kozlowski
2017-02-07 16:23   ` Arnd Bergmann
2017-02-02 18:30 ` [GIT PULL 3/4] ARM: dts: exynos: DT " Krzysztof Kozlowski
2017-02-07 14:52   ` Arnd Bergmann
2017-02-02 18:30 ` [GIT PULL 4/4] arm64: dts: exynos: DT64 " Krzysztof Kozlowski
2017-02-09 15:19   ` Arnd Bergmann
2017-02-09 18:56     ` Krzysztof Kozlowski
2017-02-10 11:30       ` Sylwester Nawrocki
2017-02-14 16:52         ` Krzysztof Kozlowski [this message]
2017-02-16 16:49           ` 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=20170214165229.y3udmy7w5gm27tys@kozik-lap \
    --to=krzk@kernel.org \
    --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