lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4e5d875c3f666be8d1c72fa19f6237f21b24f7ec.camel@sipsolutions.net>
Date: Thu, 24 Apr 2025 20:39:01 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Rob Herring <robh@...nel.org>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, david@...t.cz, Andrew Lunn	
 <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, Eric
 Dumazet	 <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo
 Abeni	 <pabeni@...hat.com>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor
 Dooley	 <conor+dt@...nel.org>, Mailing List	
 <devicetree-spec-u79uwXL29TY76Z2rM5mHXA@...lic.gmane.org>, Lorenzo Bianconi
	 <lorenzo@...nel.org>, van Spriel <arend@...adcom.com>, 
 Jérôme Pouiller	 <jerome.pouiller@...abs.com>, Bjorn
 Andersson <andersson@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>,
 Andy Gross <agross@...nel.org>, Mailing List	
 <devicetree-spec@...r.kernel.org>, netdev@...r.kernel.org, 
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-wireless@...r.kernel.org, linux-arm-msm@...r.kernel.org, Janne Grunau
	 <j@...nau.net>
Subject: Re: [PATCH v5 3/5] dt-bindings: wireless: bcm4329-fmac: Use
 wireless-controller.yaml schema

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ