[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8a665b7a-bbd0-99ce-658e-bc78568bdca2@linaro.org>
Date: Fri, 12 Aug 2022 09:57:14 +0300
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Arınç ÜNAL <arinc.unal@...nc9.com>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Sean Wang <sean.wang@...iatek.com>,
Landen Chao <Landen.Chao@...iatek.com>,
DENG Qingfang <dqfext@...il.com>,
Frank Wunderlich <frank-w@...lic-files.de>,
Luiz Angelo Daros de Luca <luizluca@...il.com>,
Sander Vanheule <sander@...nheule.net>,
René van Dorst <opensource@...rst.com>,
Daniel Golle <daniel@...rotopia.org>, erkin.bozoglu@...ont.com,
Sergio Paracuellos <sergio.paracuellos@...il.com>
Cc: netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] dt-bindings: net: dsa: mediatek,mt7530: update
json-schema
On 12/08/2022 01:09, Arınç ÜNAL wrote:
>>> -patternProperties:
>>> - "^(ethernet-)?ports$":
>>> - type: object
>>
>> Actually four patches...
>>
>> I don't find this change explained in commit msg. What is more, it looks
>> incorrect. All properties and patternProperties should be explained in
>> top-level part.
>>
>> Defining such properties (with big piece of YAML) in each if:then: is no
>> readable.
>
> I can't figure out another way. I need to require certain properties for
> a compatible string AND certain enum/const for certain properties which
> are inside patternProperties for "^(ethernet-)?port@[0-9]+$" by reading
> the compatible string.
requiring properties is not equal to defining them and nothing stops you
from defining all properties top-level and requiring them in
allOf:if:then:patternProperties.
> If I put allOf:if:then under patternProperties, I can't do the latter.
You can.
>
> Other than readability to human eyes, binding check works as intended,
> in case there's no other way to do it.
I don't see the problem in doing it and readability is one of main
factors of code admission to Linux kernel.
Best regards,
Krzysztof
Powered by blists - more mailing lists