[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a14e1b78-0f25-7f66-7969-66c3ee113025@linaro.org>
Date: Mon, 4 Jul 2022 15:48:26 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Sergiu.Moga@...rochip.com, broonie@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, Nicolas.Ferre@...rochip.com,
alexandre.belloni@...tlin.com, Claudiu.Beznea@...rochip.com
Cc: linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Kavyasree.Kotagiri@...rochip.com, UNGLinuxDriver@...rochip.com,
Tudor.Ambarus@...rochip.com
Subject: Re: [PATCH v2] spi: atmel: convert spi_atmel to json-schema
On 04/07/2022 15:32, Sergiu.Moga@...rochip.com wrote:
>>> +required:
>>> + - compatible
>>> + - reg
>>> + - interrupts
>>> + - clock-names
>>> + - clocks
>> In properties it's clock-names followed by clocks, so better to keep
>> same order here.
> I am sorry, but I don't quite understand. Isn't it the same already (the
> order in properties and the order in required)?
>>> +
Apologies, ignore my comment. I saw something else... It is fine.
Best regards,
Krzysztof
Powered by blists - more mailing lists