Hi Krzysztof, On 16/05/22 20:48, Krzysztof Kozlowski wrote: > 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@xxxxxx> >>>> --- >>>> 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. I meant order of release to market. Anyways, I'll send a patch to change the order to alphabetic order. Thanks, Kishon
