[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1eae77d7-300f-4356-c4f4-263c0d3f2bac@alliedtelesis.co.nz>
Date: Tue, 10 May 2022 00:47:23 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: Jakub Kicinski <kuba@...nel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"andrew@...n.ch" <andrew@...n.ch>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: net: orion-mdio: Convert to JSON schema
On 10/05/22 12:28, Jakub Kicinski wrote:
> On Fri, 6 May 2022 09:06:20 +1200 Chris Packham wrote:
>> Subject: [PATCH v2] dt-bindings: net: orion-mdio: Convert to JSON schema
> JSON or YAML?
I based that on other commits at that do something similar and say
"Convert to JSON schema", although I might be operating on old data.
Looking again now with `git log --oneline --no-merges --grep onvert --
Documentation/devicetree/bindings/` I see "Convert binding to YAML" and
"convert to dtschema" (still a few json-schema in there).
I guess technically the binding is written in YAML but forms part of
schema which is ultimately consumed by jsonschema but perhaps the use of
jsonschema is an implementation detail that doesn't require mentioning.
I'm happy to reword the subject and send a v3 if people feel strongly
about it.
Powered by blists - more mailing lists