linux-kernel - Re: [PATCH linux-next] clk: sparx5: Review changes

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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 28 Jul 2020 09:53:04 +0200
From:   Lars Povlsen <lars.povlsen@...rochip.com>
To:     Stephen Boyd <sboyd@...nel.org>
CC:     Arnd Bergmann <arnd@...db.de>,
        Lars Povlsen <lars.povlsen@...rochip.com>,
        SoC Team <soc@...nel.org>,
        Steen Hegelund <Steen.Hegelund@...rochip.com>,
        Microchip Linux Driver Support <UNGLinuxDriver@...rochip.com>,
        linux-clk <linux-clk@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>
Subject: Re: [PATCH linux-next] clk: sparx5: Review changes


Stephen Boyd writes:

> Quoting Arnd Bergmann (2020-07-27 13:11:49)
>> On Mon, Jul 27, 2020 at 9:39 PM Stephen Boyd <sboyd@...nel.org> wrote:
>> >
>> > Why was the clk driver merged to linux-next outside of the clk tree? Was
>> > there some sort of dependency?
>>
>> I merged the entire series of the base platform support along with
>> a few core drivers. I had asked for the series to be submitted to
>> soc@...nel.org after all parts had been reviewed, but I missed that
>> the clk driver was still missing maintainer review (I saw you had
>> reviewed some patches, but apparently that was just the binding,
>> not the driver).
>>
>> I rebased the 'arm/newsoc' branch the other day to fix another mistake,
>> so if you prefer, I can rebase it again and drop the clk driver or
>> all the sparx5 patches.
>>
>
> Yes, please just drop the clk driver and I can pick it up for the next
> merge window from the list and all the fixes can be rolled into one
> patch.

Sorry for all the commotion!

With Stephen's comments I assume I don't have to submit anything new,
at least not right now.

Otherwise, please let me know.

Cheers,

-- 
Lars Povlsen,
Microchip