linux-kernel - Re: [PATCH 1/1] dt-bindings: net: dsa: nxp,sja1105: Add optional clock

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: <20251015072547.40c38a2f@kernel.org>
Date: Wed, 15 Oct 2025 07:25:47 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Rob Herring <robh@...nel.org>
Cc: Conor Dooley <conor@...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 Wed, 15 Oct 2025 06:53:01 -0500 Rob Herring wrote:
> > > 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>  
> >
> > We crossed replies, do you mind
> >
> >   pw-bot: xyz [project]
> >
> > ? I like the optional param after required, and the brackets may help
> > us disambiguate between optional params if there are more in the future.  
> 
> That's fine. Though it will be optional for you, but not us? We have
> to ignore tags without the project if tags intended for netdev are
> continued without the project. Or does no project mean I want to
> update every project?

Fair :( I imagine your workflow is that patches land in your pw, and
once a DT maintainer reviewed them you don't care about them any more?
So perhaps a better bot on your end would be a bot which listens to
Ack/Review tags from DT maintainers. When tag is received the patch
gets dropped from PW as "Handled Elsewhere", and patch id (or whatever 
that patch hash thing is called) gets recorded to automatically discard
pure reposts.

Would that work?