From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nate Drude <nate.d@variscite.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Eran Matityahu <eran.m@variscite.com>
Subject: Re: [PATCH] dt-bindings: add device tree bindings for mxl-8611x PHY
Date: Sun, 16 Jul 2023 18:31:38 +0200 [thread overview]
Message-ID: <08ae1b98-5bf8-d165-47b5-f9e7cdca8898@kernel.org> (raw)
In-Reply-To: <94e84ae4-f8e3-2bd1-b876-9301a1d6cc78@variscite.com>
On 14/07/2023 14:53, Nate Drude wrote:
>
> Once again, thanks for your review. Hopefully when the driver patches
> are sent for Linux this will have been helpful.
Driver patches are not really necessary here and I would say are
independent. So as I said - submit bindings to the Linux kernel, so they
will get proper review. Otherwise it does not matter what I say here. It
does not guarantee absolutely any stable bindings because whatever
someone submits to Linux kernel will later overrule it. Therefore I do
not see any benefit of your approach - you will not be able to create
Linux kernel ABI (bindings) by sending binding patch to U-Boot. It does
not work like that.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-07-16 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 13:20 [PATCH] Requesting review of U-Boot mxl-8611x device tree bindings Nate Drude
2023-07-13 13:23 ` [PATCH] dt-bindings: add device tree bindings for mxl-8611x PHY Nate Drude
2023-07-13 19:06 ` Krzysztof Kozlowski
2023-07-14 12:53 ` Nate Drude
2023-07-16 16:31 ` Krzysztof Kozlowski [this message]
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=08ae1b98-5bf8-d165-47b5-f9e7cdca8898@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eran.m@variscite.com \
--cc=nate.d@variscite.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).