linux-kernel - Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs

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: <81d94ea8-9d0f-785b-07aa-fe9c9093ad73@linaro.org>
Date:   Mon, 16 May 2022 17:18:43 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Kishon Vijay Abraham I <kishon@...com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Nishanth Menon <nm@...com>
Cc:     Santosh Shilimkar <ssantosh@...nel.org>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org,
        Vignesh Raghavendra <vigneshr@...com>
Subject: Re: [PATCH 1/2] dt-bindings: soc: ti: pruss: Update bindings for K3
 AM62x SoCs

On 16/05/2022 14:33, Kishon Vijay Abraham I wrote:
> Hi Krzysztof,
> 
> On 28/04/22 11:48, Krzysztof Kozlowski wrote:
>> On 27/04/2022 09:27, Kishon Vijay Abraham I wrote:
>>> Update the PRUSS bindings for the PRUSSM instance present in
>>> AM625 SoC.
>>>
>>> Signed-off-by: Kishon Vijay Abraham I <kishon@...com>
>>> ---
>>>  Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> index 64461d432004..cf13e5179657 100644
>>> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> @@ -69,6 +69,7 @@ properties:
>>>        - ti,am654-icssg   # for K3 AM65x SoC family
>>>        - ti,j721e-icssg   # for K3 J721E SoC family
>>>        - ti,am642-icssg   # for K3 AM64x SoC family
>>> +      - ti,am625-pruss   # for K3 AM62x SoC family
>>>  
>>
>> Looks like out of order (although for some reason before it was also
>> misordered...).
> 
> These are really in the chronological order of the introduction of SoCs.
> Isn't that okay to have?

You mean order of release on the market of order of adding files here?
The first is ok, the latter would mean there is no order at all.

It's a nit, so I don't expect to change it. It just increases our
chances for conflicts...


Best regards,
Krzysztof