public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/5] ARM: dts: exynos: Artik5 topic branch for v4.7
Date: Mon, 25 Apr 2016 17:53:02 +0200	[thread overview]
Message-ID: <5431726.aFYokxb3m1@wuerfel> (raw)
In-Reply-To: <571DDCE5.5020201@samsung.com>

On Monday 25 April 2016 11:01:25 Krzysztof Kozlowski wrote:
> On 04/24/2016 11:15 PM, Arnd Bergmann wrote:
> > On Wednesday 13 April 2016 12:01:18 Krzysztof Kozlowski wrote:
> >> Topic branch for Device Tree changes for Exynos 3250 for v4.7:
> >>
> >> Merge necessary new clocks from Sylwester (used by new board) and add support
> >> for Exynos3250-based Artik5 board.
> >>
> > 
> > Merged into next/dt, thanks!
> > 
> > I see that you have modified the include/dt-bindings/clock/exynos3250.h
> > file. Two questions about that:
> > 
> > - How is this going to get synchronized with the respective driver changes
> >   in a way that avoids breaking the build of the clk tree? Do you just
> >   wait another merge window for that?
> 
> Mentioned include/dt-bindings change comes from clk tree, merged here
> (see "Merge tag 'clk-v4.7-exynos3250' of
> git://linuxtv.org/snawrocki/samsung into
> for-v4.7/dt-exynos3250-artik5"). I assume that any driver related
> changes in clk tree would be on top of that commit.


Ok

> > - Are there any other clocks that you should define now so you don't run
> >   into dependency problems later?
> 
> Indeed we might have similar for Exynos5422 and devfreq but I already
> talked with Sylwester about it. He pushed such changes to clk folks and
> prepared a tag for me - just in case:
> https://lkml.org/lkml/2016/4/15/561
> 

Very good, thanks!

	Arnd

  reply	other threads:[~2016-04-25 15:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 10:01 [GIT PULL 0/5] ARM: EXYNOS: Stuff for v4.7 Krzysztof Kozlowski
2016-04-13 10:01 ` [GIT PULL 1/5] ARM: dts: exynos: Artik5 topic branch " Krzysztof Kozlowski
2016-04-24 21:15   ` Arnd Bergmann
2016-04-25  9:01     ` Krzysztof Kozlowski
2016-04-25 15:53       ` Arnd Bergmann [this message]
2016-04-13 10:01 ` [GIT PULL 2/5] ARM: dts: exynos: DT " Krzysztof Kozlowski
2016-04-24 21:18   ` Arnd Bergmann
2016-04-25  9:02     ` Krzysztof Kozlowski
2016-04-13 10:01 ` [GIT PULL 3/5] arm64: " Krzysztof Kozlowski
2016-04-25 20:48   ` Arnd Bergmann
2016-04-13 10:01 ` [GIT PULL 4/5] ARM: defconfig " Krzysztof Kozlowski
2016-04-25 19:08   ` Arnd Bergmann
2016-04-13 10:01 ` [GIT PULL 5/5] arm64: " Krzysztof Kozlowski
2016-04-25 19:18   ` 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=5431726.aFYokxb3m1@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