From: Johannes Berg <johannes@sipsolutions.net>
To: Rob Herring <robh@kernel.org>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
david@ixit.cz, "Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Mailing List"
<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Lorenzo Bianconi" <lorenzo@kernel.org>,
"van Spriel" <arend@broadcom.com>,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Andy Gross" <agross@kernel.org>,
"Mailing List" <devicetree-spec@vger.kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-arm-msm@vger.kernel.org, "Janne Grunau" <j@jannau.net>
Subject: Re: [PATCH v5 3/5] dt-bindings: wireless: bcm4329-fmac: Use wireless-controller.yaml schema
Date: Thu, 24 Apr 2025 20:39:01 +0200 [thread overview]
Message-ID: <4e5d875c3f666be8d1c72fa19f6237f21b24f7ec.camel@sipsolutions.net> (raw)
In-Reply-To: <CAL_JsqKGmoiW=yDD7G4Qznsa7S2wQ7x4Mh0i4puAyFsvcnHz1A@mail.gmail.com>
On Thu, 2025-04-24 at 13:26 -0500, Rob Herring wrote:
> While it seems the reviews of the series caused more warnings for
> Apple, in general, schemas creating warnings is not breaking things.
> In a way, the whole point is to create warnings because if the .dts
> files were perfect already we wouldn't need schemas. The main
> requirement for schemas is only that they don't create warnings for
> the examples. There's still too many for .dts files to worry about it
> (and there's intermittent warnings from things getting merged via
> different trees).
>
Oh, sure, but now if you want to apply the fixes you probably have to
wait for the broken patches in my tree to percolate all the way through
to Linus, then back to your tree, and then you can apply the fixes?
Seemed it'd be easier to send the fixes to me but it's all your call,
just let me know what you prefer.
johannes
next prev parent reply other threads:[~2025-04-24 18:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 17:41 [PATCH v5 0/5] dt-bindings: net: Add network-class.yaml schema David Heidelberg via B4 Relay
2025-03-24 17:41 ` [PATCH v5 1/5] dt-bindings: net: Add network-class schema for mac-address properties David Heidelberg via B4 Relay
2025-03-24 22:59 ` Rob Herring
2025-03-24 17:41 ` [PATCH v5 2/5] dt-bindings: net: Add generic wireless controller David Heidelberg via B4 Relay
2025-03-24 17:41 ` [PATCH v5 3/5] dt-bindings: wireless: bcm4329-fmac: Use wireless-controller.yaml schema David Heidelberg via B4 Relay
2025-04-24 8:20 ` Krzysztof Kozlowski
2025-04-24 8:28 ` Krzysztof Kozlowski
2025-04-24 12:09 ` Johannes Berg
2025-04-24 15:37 ` Krzysztof Kozlowski
2025-04-24 15:42 ` Johannes Berg
2025-04-24 18:26 ` Rob Herring
2025-04-24 18:39 ` Johannes Berg [this message]
2025-04-24 19:04 ` Rob Herring
2025-04-24 19:06 ` Johannes Berg
2025-03-24 17:41 ` [PATCH v5 4/5] dt-bindings: wireless: silabs,wfx: Use wireless-controller.yaml David Heidelberg via B4 Relay
2025-03-24 17:41 ` [PATCH v5 5/5] dt-bindings: wireless: qcom,wcnss: " David Heidelberg via B4 Relay
2025-03-25 10:33 ` [PATCH v5 0/5] dt-bindings: net: Add network-class.yaml schema Johannes Berg
2025-03-25 13:02 ` Rob Herring
2025-03-25 13:11 ` Johannes Berg
2025-03-26 23:08 ` David Heidelberg
2025-03-26 23:14 ` Johannes Berg
2025-03-28 19:52 ` David Heidelberg
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=4e5d875c3f666be8d1c72fa19f6237f21b24f7ec.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arend@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=j@jannau.net \
--cc=jerome.pouiller@silabs.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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).