From: Tom Rini <trini@konsulko.com>
To: Rob Herring <robh@kernel.org>, Simon Glass <sjg@chromium.org>
Cc: devicetree@vger.kernel.org,
U-Boot Mailing List <u-boot@lists.denx.de>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v3] schemas: Add schema for U-Boot driver model 'phase tags'
Date: Mon, 10 Oct 2022 12:55:03 -0400 [thread overview]
Message-ID: <20221010165503.GN2020586@bill-the-cat> (raw)
In-Reply-To: <CAL_JsqLF4J1UeuYtE_SHUVsFTuwd-THK6KX=E1wU03hnZB7X9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Mon, Oct 10, 2022 at 11:34:00AM -0500, Rob Herring wrote:
> On Tue, Oct 4, 2022 at 6:22 PM Simon Glass <sjg@chromium.org> wrote:
> >
> > Until recently it has not been possible to add any U-Boot-specific
> > properties to the device tree schema. Now that it is somewhat separated
> > from Linux and people are feeling the enormous pain of the bifurcated
> > schema, it seems like a good time to add this and other U-Boot-specific
> > bindings.
>
> It's been possible provided there was agreement on the properties.
> There just wasn't in this case.
To jump on this part at least, I feel (but human memory is not the
most reliable) it being a bit more than that, but, that's history and
we're all moving forward now. I think for v4 the commit message needs
to be edited to remove the historical sentiment and just state what
we're adding and why / who it's useful for.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-10-10 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 23:22 [PATCH v3] schemas: Add schema for U-Boot driver model 'phase tags' Simon Glass
2022-10-05 2:11 ` Sean Anderson
2022-10-10 16:34 ` Rob Herring
2022-10-10 16:55 ` Tom Rini [this message]
2022-10-10 17:13 ` Tom Rini
2022-10-13 3:19 ` Simon Glass
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=20221010165503.GN2020586@bill-the-cat \
--to=trini@konsulko.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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