From: Aleksei Sviridkin <f@lex.la>
To: Paolo Abeni <pabeni@redhat.com>
Cc: theo.lebrun@bootlin.com, conor.dooley@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux@armlinux.org.uk,
vineeth.karumanchi@amd.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Aleksei Sviridkin <f@lex.la>
Subject: Re: [PATCH net v2 1/2] net: macb: zero the link settings taprio reads back
Date: Tue, 8 Sep 2026 15:32:53 +0000 [thread overview]
Message-ID: <20260908153253.4144665-1-f@lex.la> (raw)
In-Reply-To: <6cfd72f7-b6da-45ef-886a-7703027a55f9@redhat.com>
On Tue, Sep 08, 2026 at 11:44:55AM +0200, Paolo Abeni wrote:
> Not blocking the series for this, but note that you should actually
> specify the model you used.
I took the bare form from coding-assistants.rst, which asks for
"Assisted-by: LLM" since 816d9992d9ed ("coding-assistants: simplify
attribution"). The reasoning there makes sense to me: naming the model
advertises the vendor and says little about the patch. Does netdev have
its own rule on top of that?
The other half I am unsure about is the routing. The work goes through a
router, so an honest tag on one of these patches would name seven models
from three vendors. How is that meant to be written?
next prev parent reply other threads:[~2026-09-08 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 12:36 [PATCH net v2 0/2] net: macb: fix the link speed the taprio setup reads Aleksei Sviridkin
2026-09-03 12:36 ` [PATCH net v2 1/2] net: macb: zero the link settings taprio reads back Aleksei Sviridkin
2026-09-08 9:44 ` Paolo Abeni
2026-09-08 15:32 ` Aleksei Sviridkin [this message]
2026-09-08 17:18 ` Paolo Abeni
2026-09-03 12:36 ` [PATCH net v2 2/2] net: macb: reject an unknown link speed in the taprio setup Aleksei Sviridkin
2026-09-08 10:00 ` [PATCH net v2 0/2] net: macb: fix the link speed the taprio setup reads 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=20260908153253.4144665-1-f@lex.la \
--to=f@lex.la \
--cc=andrew+netdev@lunn.ch \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=theo.lebrun@bootlin.com \
--cc=vineeth.karumanchi@amd.com \
/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®