linux-kernel - Re: [GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round

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] [day] [month] [year] [list]

Message-ID: <CAK8P3a1Q=6V07ORhEkA3MDd9OwRw4BHu91-uYyFd8MgLvggSig@mail.gmail.com>
Date:   Thu, 16 Feb 2017 17:49:18 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Krzysztof Kozlowski <krzk@...nel.org>
Cc:     Sylwester Nawrocki <s.nawrocki@...sung.com>,
        linux-samsung-soc@...r.kernel.org,
        Kevin Hilman <khilman@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Javier Martinez Canillas <javier@....samsung.com>,
        arm-soc <arm@...nel.org>, Kukjin Kim <kgene@...nel.org>,
        Olof Johansson <olof@...om.net>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round

On Tue, Feb 14, 2017 at 5:52 PM, Krzysztof Kozlowski <krzk@...nel.org> wrote:
> 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:
>>
>> > 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?

Sorry, I haven't had a chance to discuss with Olof how we want to proceed.
I've pulled it into a next/late branch for now, which is similar to what we
did in the past, and we may or may not send it after the other pull
requests.

There is one other platform that has a similar problem and I'll pull that
in the same branch, while all the others have been able to rework their
trees to avoid it for 4.11.

      Arnd