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: <20251014204807.GA1075103-robh@kernel.org>
Date: Tue, 14 Oct 2025 15:48:07 -0500
From: Rob Herring <robh@...nel.org>
To: Conor Dooley <conor@...nel.org>
Cc: Jakub Kicinski <kuba@...nel.org>, Frank Li <Frank.Li@....com>,
	Andrew Lunn <andrew@...n.ch>, Vladimir Oltean <olteanv@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	"open list:NETWORKING DRIVERS" <netdev@...r.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>,
	open list <linux-kernel@...r.kernel.org>, imx@...ts.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: net: dsa: nxp,sja1105: Add optional
 clock

On Tue, Oct 14, 2025 at 08:35:04PM +0100, Conor Dooley wrote:
> On Tue, Oct 14, 2025 at 12:02:13PM -0700, Jakub Kicinski wrote:
> > On Tue, 14 Oct 2025 19:12:23 +0100 Conor Dooley wrote:
> > > On Tue, Oct 14, 2025 at 07:02:50PM +0100, Conor Dooley wrote:
> > > > On Fri, Oct 10, 2025 at 02:34:17PM -0400, Frank Li wrote:  
> > > > > Add optional clock for OSC_IN and fix the below CHECK_DTBS warnings:
> > > > >   arch/arm/boot/dts/nxp/imx/imx6qp-prtwd3.dtb: switch@0 (nxp,sja1105q): Unevaluated properties are not allowed ('clocks' was unexpected)
> > > > > 
> > > > > Signed-off-by: Frank Li <Frank.Li@....com>  
> > > > 
> > > > Acked-by: Conor Dooley <conor.dooley@...rochip.com>
> > > > pw-bot: not-applicable  
> > > 
> > > Hmm, I think this pw-bot command, intended for the dt patchwork has
> > > probably screwed with the state in the netdev patchwork. Hopefully I can
> > > fix that via
> > 
> > The pw-bot commands are a netdev+bpf thing :) They won't do anything
> > to dt patchwork. IOW the pw-bot is a different bot than the one that
> > replies when patch is applied.
> 
> Rob's recently added it to our patchwork too.

And the issue is that both PW projects might get updated and both don't 
necessarily want the same state (like this case). So we need to 
distinguish. Perhaps like one of the following:

dt-pw-bot: <state>

or

pw-bot: <project> <state>

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ