From: Jakub Kicinski <kuba@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Conor Dooley <conor@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: net: dsa: nxp,sja1105: Add optional clock
Date: Tue, 14 Oct 2025 18:13:02 -0700 [thread overview]
Message-ID: <20251014181302.44537f00@kernel.org> (raw)
In-Reply-To: <20251014204807.GA1075103-robh@kernel.org>
On Tue, 14 Oct 2025 15:48:07 -0500 Rob Herring wrote:
> 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:
> > > 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>
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.
next prev parent reply other threads:[~2025-10-15 1:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 18:34 [PATCH 1/1] dt-bindings: net: dsa: nxp,sja1105: Add optional clock Frank Li
2025-10-14 18:02 ` Conor Dooley
2025-10-14 18:12 ` Conor Dooley
2025-10-14 19:02 ` Jakub Kicinski
2025-10-14 19:35 ` Conor Dooley
2025-10-14 20:40 ` Jakub Kicinski
2025-10-14 20:48 ` Rob Herring
2025-10-15 1:13 ` Jakub Kicinski [this message]
2025-10-15 11:53 ` Rob Herring
2025-10-15 12:09 ` Andrew Lunn
2025-10-15 14:25 ` Jakub Kicinski
2025-10-15 17:32 ` Rob Herring
2025-10-15 17:53 ` Jakub Kicinski
2025-10-15 21:56 ` Conor Dooley
2025-10-14 20:07 ` Vladimir Oltean
2025-10-15 16:00 ` patchwork-bot+netdevbpf
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=20251014181302.44537f00@kernel.org \
--to=kuba@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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).