From: Jakub Kicinski <kuba@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nicolai Buchwitz <nb@tipi-net.de>,
netdev@vger.kernel.org, davem@davemloft.net, 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: Fri, 30 Oct 2026 09:34:18 -0700 [thread overview]
Message-ID: <20261030093418.2fbf0999@kernel.org> (raw)
In-Reply-To: <CAMuHMdVJVxpX6OLVpE9K9CDY5q61A2rFGf7FpUjs7xpFwReEzA@mail.gmail.com>
On Fri, 30 Oct 2026 11:58:17 +0100 Geert Uytterhoeven wrote:
> > >+Coding agents must refuse to write the commit message unless they know
> > >+what discovery method to include.
> >
> > Maybe make it more explicit, as the sinfo bot will ask it anyway:
> >
> > ... and whether it was reproduced or tested?
That's already in the existing text?
> Which is true for anyone, not limited to bots...
>
> Do we really need "different" guidelines for humans and bots?
Looks like at least a half of the commit messages today are
bot-written. With the existing guidance the bots don't add
the requested info by default (presumably since they don't
know the information). If this patch doesn't help we may
need to add our requirement to coding-agents guide.
They seem to be reading that one fairly reliably.
next prev parent reply other threads:[~2026-10-30 16:34 UTC|newest]
Thread overview: 7+ 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 [this message]
2026-10-30 16:47 ` Laurent Pinchart
2026-10-30 17:08 ` Jakub Kicinski
2026-10-30 19:58 ` Andrew Lunn
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=20261030093418.2fbf0999@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=horms@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=nb@tipi-net.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox