linux-kernel - Re: [PATCH v1] dt-bindings: clock: convert rockchip,rk3128-cru.txt to YAML

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: <1754977.TLkxdtWsSY@phil>
Date:   Sat, 17 Sep 2022 08:56:48 +0200
From:   Heiko Stuebner <heiko@...ech.de>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Johan Jonker <jbx6244@...il.com>
Cc:     zhangqing@...k-chips.com, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, sboyd@...nel.org,
        mturquette@...libre.com, linux-clk@...r.kernel.org,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] dt-bindings: clock: convert rockchip,rk3128-cru.txt to YAML

Am Mittwoch, 14. September 2022, 11:25:48 CEST schrieb Johan Jonker:
> 
> On 9/12/22 12:51, Krzysztof Kozlowski wrote:
> > On 11/09/2022 23:20, Johan Jonker wrote:
> >> Convert rockchip,rk3128-cru.txt to YAML.
> >>
> >> Signed-off-by: Johan Jonker <jbx6244@...il.com>
> > 
> > Thank you for your patch. There is something to discuss/improve.
> > 
> >> diff --git a/Documentation/devicetree/bindings/clock/rockchip,rk3128-cru.yaml b/Documentation/devicetree/bindings/clock/rockchip,rk3128-cru.yaml
> >> new file mode 100644
> >> index 000000000..03e5d7f0e
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/clock/rockchip,rk3128-cru.yaml
> >> @@ -0,0 +1,73 @@
> >> +# SPDX-License-Identifier: GPL-2.0
> > 
> 
> > Can't it be Dual licensed?
> 
> That depends on Heiko and Rockchip.
> I can produce the patch for it, but I'm not in control whether they reply or not. 

Rockchip recently replied on other clock-patches to dual-license the
binding, so this will be ok [0] .

And for me, following in-kernel policies more, is always acceptable :-)

Heiko

[0] https://lore.kernel.org/all/510d1180-bc8e-7820-c772-ed7f35447087@rock-chips.com/
>From Finley with an  @rock-chips.com address, so this should be ok