From: Rob Herring <robh@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>, Jakub Kicinski <kuba@kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
krzysztof.kozlowski+dt@linaro.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: net: orion-mdio: Convert to JSON schema
Date: Mon, 16 May 2022 13:14:40 -0500 [thread overview]
Message-ID: <20220516181440.GA2997786-robh@kernel.org> (raw)
In-Reply-To: <Ynm0tm7/05ye9z6v@lunn.ch>
On Tue, May 10, 2022 at 02:41:26AM +0200, Andrew Lunn wrote:
> On Mon, May 09, 2022 at 05:28:14PM -0700, 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 actually prefer 'DT schema format' which implicitly means json-schema
vocabulary in YAML formatted files (among other constraints we place on
them).
>
> JAML is a superset of JSON. So it is not completely wrong. I've no
> idea if this particular binding sticks to the subset which is JSON.
I think you just invented a new term for 'JSON compatible YAML subset'.
Rob
next prev parent reply other threads:[~2022-05-16 18:14 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 [this message]
2022-05-10 0:47 ` Chris Packham
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=20220516181440.GA2997786-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--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 \
/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).