linux-kernel - Re: [PATCH v2 0/5] update Mediatek MT2712 clock and scpsys support

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]

Date:   Tue, 17 Apr 2018 16:22:50 +0200
From:   Matthias Brugger <matthias.bgg@...il.com>
To:     Stephen Boyd <sboyd@...nel.org>,
        Stephen Boyd <sboyd@...eaurora.org>,
        Weiyi Lu <weiyi.lu@...iatek.com>, Arnd Bergmann <arnd@...db.de>
Cc:     Mike Turquette <mturquette@...libre.com>,
        Rob Herring <robh@...nel.org>,
        James Liao <jamesjj.liao@...iatek.com>,
        Fan Chen <fan.chen@...iatek.com>, devicetree@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-mediatek@...ts.infradead.org, linux-clk@...r.kernel.org,
        srv_heupstream@...iatek.com
Subject: Re: [PATCH v2 0/5] update Mediatek MT2712 clock and scpsys support



On 03/21/2018 10:11 AM, Matthias Brugger wrote:
> 
> 
> On 03/20/2018 08:23 AM, Stephen Boyd wrote:
>> Quoting Weiyi Lu (2018-03-19 23:07:48)
>>> On Mon, 2018-03-12 at 15:03 +0800, Weiyi Lu wrote:
>>>> This series is based on v4.16-rc1 and composed of scpsys control (PATCH 1-2) and clock control (PATCH 3-5).
>>>> Basically, all changes are for the ECO design change of MT2712.
>>>>
>>>> changes since v1:
>>>> - Avoid renumbering clocks. Append new clocks at the bottom of each own subsystem.
>>>>
>>> Hi Matthias & Stephen,
>>>
>>> Sorry to bother. Just saw patch 1/2 are already pushed to v4.16-next-soc
>>> and patch 3/5 are applied onto clk-next. What about the patch 4(arm64:
>>> dts: add clock device nodes of MT2712). Does there any problem remain or
>>> it cause some problems? Many thanks.
>>
>> Patch 4 can go via arm-soc? I'm not planning to apply that patch.
>>
> 
> I can take it through my branch, no problem. But I think it is too late for this
> cycle. CCing Arnd to confirm.
> 

Now pushed to v4.17-next/dts64

Thanks a lot.