From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net] docs: netdev: try to force agents to disclose info for fixes
Date: Tue, 03 Nov 2026 12:00:07 +0000 [thread overview]
Message-ID: <179370720733.1083709.17569222025256007017.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261029153459.2257998-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 29 Oct 2026 08:34:58 -0700 you wrote:
> "LLM-driven-developers" are not including the info about discovery
> method we want to see in commit messages. Try to add more forceful
> language to make agents ask for it. claude and codex seem to load
> maintainer-netdev.rst already.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net] docs: netdev: try to force agents to disclose info for fixes
https://git.kernel.org/netdev/net/c/f56daaadfeca
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-03 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 15:34 [PATCH net] docs: netdev: try to force agents to disclose info for fixes Jakub Kicinski
2026-10-29 18:50 ` Nicolai Buchwitz
2026-10-30 10:58 ` Geert Uytterhoeven
2026-10-30 16:34 ` Jakub Kicinski
2026-10-30 16:47 ` Laurent Pinchart
2026-10-30 17:08 ` Jakub Kicinski
2026-10-30 19:58 ` Andrew Lunn
2026-11-03 11:53 ` Paolo Abeni
2026-11-03 12:00 ` patchwork-bot+netdevbpf [this message]
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=179370720733.1083709.17569222025256007017.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.