linux-kernel - Re: [RFC v2 1/2] clk: hisilicon: add CRG driver Hi3521a SoC

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]

Message-ID: <b1b87be5-a048-b713-c9f2-84b948aa6718@linaro.org>
Date:   Thu, 2 Jun 2022 08:37:43 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     "Marty E. Plummer" <hanetzer@...rtmail.com>
Cc:     arnd@...db.de, cai.huoqing@...ux.dev, christian.koenig@....com,
        devicetree@...r.kernel.org, gengdongjiu@...wei.com,
        krzysztof.kozlowski+dt@...aro.org,
        linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
        linux@...linux.org.uk, michael@...le.cc, miquel.raynal@...tlin.com,
        mturquette@...libre.com, novikov@...ras.ru, olof@...om.net,
        p.yadav@...com, rdunlap@...radead.org, richard@....at,
        robh+dt@...nel.org, sboyd@...nel.org, soc@...nel.org,
        sumit.semwal@...aro.org, tudor.ambarus@...rochip.com,
        vigneshr@...com, xuwei5@...ilicon.com
Subject: Re: [RFC v2 1/2] clk: hisilicon: add CRG driver Hi3521a SoC

On 01/06/2022 20:24, Marty E. Plummer wrote:

>>> Either or. Whatever makes the workload easier is what I'm looking for.
>>
>> Sorry, you need to be more specific. Apply is not a job for you, for the
>> patch submitter.
>>
>> Then you miss here important piece - which is the first patch. DTS goes
>> always via separate branch (or even tree) from driver changes. That's
>> why bindings are always separate first patches.
>>
> So, add a 4: arch/arm/boot/dts/soc.dtsi and 5: arch/arm/boot/dts/board.dts
> to the above list, or should those be the same patch as well?

For me does not matter, sub architecture maintainer might have preference.

Best regards,
Krzysztof