From: Tom Rini <trini@konsulko.com>
To: Nishanth Menon <nm@ti.com>
Cc: Neha Malcom Francis <n-francis@ti.com>,
sjg@chromium.org, u-boot@lists.denx.de, vigneshr@ti.com,
u-kumar1@ti.com, reidt@ti.com, m-chawdhry@ti.com
Subject: Re: [PATCH 1/2] dt-bindings: misc: Move esm-k3.txt to ti,j721e-esm.yaml
Date: Tue, 14 Nov 2023 08:37:16 -0500 [thread overview]
Message-ID: <20231114133716.GQ6601@bill-the-cat> (raw)
In-Reply-To: <20231113195216.m7itxtjh467vv3yr@equity>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On Mon, Nov 13, 2023 at 01:52:16PM -0600, Nishanth Menon wrote:
> On 10:00-20231113, Neha Malcom Francis wrote:
> > Move esm-k3.txt to ti,j721e-esm.yaml in line with the devicetree
> > documentation in kernel.
> >
> > Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
> > ---
> > doc/device-tree-bindings/misc/esm-k3.txt | 25 ---------
> > .../misc/ti,j721e-esm.yaml | 53 +++++++++++++++++++
>
> What is the rule here?
> https://tgit.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/misc/ti,j721e-esm.yaml
> we have the binding in upstream kernel.
Not to cause anyone undue worry but part of me wants to just
submodule/subtree
https://github.com/devicetree-org/dt-schema/tree/main/dtschema/schemas
as that looks like Rob syncs it with the kernel periodically and since
in turn we're working with Rob to upstream our unique bindings there
here and not there list should be shrinking, not growing. Since we say
"use the kernel device trees" and we don't have the validation make
targets, the content of the copies of the schema in our trees is more of
a promise that it's true than used anywhere. So perhaps it would be
better if something was written down to that effect.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-11-14 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 4:30 [PATCH 0/2] J721E DTS Sync with Kernel v6.7-rc1 Neha Malcom Francis
2023-11-13 4:30 ` [PATCH 1/2] dt-bindings: misc: Move esm-k3.txt to ti,j721e-esm.yaml Neha Malcom Francis
2023-11-13 19:52 ` Nishanth Menon
2023-11-14 13:37 ` Tom Rini [this message]
2023-11-13 23:59 ` Tom Rini
2023-11-22 20:49 ` Tom Rini
2023-11-13 4:30 ` [PATCH 2/2] arm: dts: k3-j721e-*: Sync with kernel v6.7-rc1 Neha Malcom Francis
2023-11-22 20:49 ` Tom Rini
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=20231114133716.GQ6601@bill-the-cat \
--to=trini@konsulko.com \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=reidt@ti.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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