From: Andrew Lunn <andrew@lunn.ch>
To: Rob Herring <robh@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>, Conor Dooley <conor@kernel.org>,
Frank Li <Frank.Li@nxp.com>, 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 14:09:11 +0200 [thread overview]
Message-ID: <0d90ce60-a7cd-4fff-9db2-489531e3c944@lunn.ch> (raw)
In-Reply-To: <CAL_Jsq+SSiMCbGvbYcrS1mGUJOakqZF=gZOJ4iC=Y5LbcfTAUQ@mail.gmail.com>
> I also considered looking at who the email is from and restricting it
> to the maintainers. I know the netdev one doesn't do that either
> because I used it a couple of times. :) It does seem like it could be
> abused.
The netdev one does have some restrictions.
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#updating-patch-status
says:
The use of the bot is restricted to authors of the patches (the
From: header on patch submission and command must match!),
maintainers of the modified code according to the MAINTAINERS file
(again, From: must match the MAINTAINERS entry) and a handful of
senior reviewers.
Here is one example from you:
https://patchwork.kernel.org/project/netdevbpf/patch/20241113225742.1784723-2-robh@kernel.org/
and it was your own patch.
All its actions are logged:
https://netdev.bots.linux.dev/pw-bot.html
so we can keep an eye of out for abuse. Plus, since it is an email to
patchwork, patchwork itself should have any abuse emails.
Andrew
next prev parent reply other threads:[~2025-10-15 12:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 18:34 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 [this message]
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=0d90ce60-a7cd-4fff-9db2-489531e3c944@lunn.ch \
--to=andrew@lunn.ch \
--cc=Frank.Li@nxp.com \
--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=kuba@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
all inboxes | Powered by JetHome®