linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: net: orion-mdio: Convert to JSON schema
Date: Tue, 10 May 2022 00:47:23 +0000	[thread overview]
Message-ID: <1eae77d7-300f-4356-c4f4-263c0d3f2bac@alliedtelesis.co.nz> (raw)
In-Reply-To: <20220509172814.31f83802@kernel.org>


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.

  parent reply	other threads:[~2022-05-10  0:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 21:06 [PATCH v2] dt-bindings: net: orion-mdio: Convert to JSON schema Chris Packham
2022-05-10  0:28 ` Jakub Kicinski
2022-05-10  0:41   ` Andrew Lunn
2022-05-10  0:43     ` Jakub Kicinski
2022-05-16 18:14     ` Rob Herring
2022-05-10  0:47   ` Chris Packham [this message]
2022-05-10 23:12 ` Andrew Lunn
2022-05-11  2:20 ` patchwork-bot+netdevbpf
2022-05-16 18:16 ` Rob Herring
2022-05-16 22:18   ` Chris Packham
2022-05-16 22:27     ` Chris Packham
2022-05-18 16:18       ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1eae77d7-300f-4356-c4f4-263c0d3f2bac@alliedtelesis.co.nz \
    --to=chris.packham@alliedtelesis.co.nz \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).