devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 15 Oct 2025 10:53:23 -0700	[thread overview]
Message-ID: <20251015105323.7342652f@kernel.org> (raw)
In-Reply-To: <CAL_Jsq+wHG_DW1D_=dR6Q_mwyqFAXKGx771PsqjvW+XCRKM3tw@mail.gmail.com>

On Wed, 15 Oct 2025 12:32:14 -0500 Rob Herring wrote:
> On Wed, Oct 15, 2025 at 9:25 AM Jakub Kicinski <kuba@kernel.org> wrote:
> > On Wed, 15 Oct 2025 06:53:01 -0500 Rob Herring wrote:  
> > > 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?  
> 
> Not exactly. Often I don't, but for example sometimes I need to apply
> the patch (probably should setup a group tree, but it's enough of an
> exception I haven't.).
> 
> > 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.  
> 
> I already have that in place too. Well, kind of, it updates my
> review/ack automatically on subsequent versions, but I currently do a
> separate pass of what Conor and Krzysztof reviewed. Where the pw-bot
> tags are useful is when there are changes requested. I suppose I could
> look for replies from them without acks, but while that usually
> indicates changes are needed, not always. So the pw-bot tag is useful
> to say the other DT maintainers don't need to look at this patch at
> all.

I don't think we need to do anything, then. Changes-requested will 
apply across all the patchwork instances. Only not-applicable /
handled-elsewhere gets tricky with multiple instances.

  reply	other threads:[~2025-10-15 17:53 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
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 [this message]
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=20251015105323.7342652f@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).