linux-kernel - Re: [GIT PULL 1/5] ARM: dts: exynos: Artik5 topic branch for v4.7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Apr 2016 17:53:02 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	linux-samsung-soc@...r.kernel.org,
	Kevin Hilman <khilman@...nel.org>,
	linux-kernel@...r.kernel.org, arm@...nel.org,
	Kukjin Kim <kgene@...nel.org>, Olof Johansson <olof@...om.net>
Subject: Re: [GIT PULL 1/5] ARM: dts: exynos: Artik5 topic branch for v4.7

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