From: Jakub Kicinski <kuba@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: Matthieu Baerts <matttbe@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Jakub Raczynski <j.raczynski@samsung.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH net-next 2/2] docs: netdev: clarify expected interactions with LLMs
Date: Fri, 14 Aug 2026 12:07:50 -0700 [thread overview]
Message-ID: <20260814120750.420d75d1@kernel.org> (raw)
In-Reply-To: <an8OY1XeDr1ajATf@fedora>
On Fri, 14 Aug 2026 20:47:31 +0800 Hangbin Liu wrote:
> I think the ideal way is for the result to be subscribed to.
It'd be ideal if y'all run the LLMs locally before sending the patches..
I understand that it's not always possible, but let's be clear on what
the priorities are - as you say netdev@ is already too busy, we don't
want the buggy submissions in the first place, _ideally_.
next prev parent reply other threads:[~2026-08-14 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 9:24 [PATCH net-next 0/2] docs: netdev: a couple of updates Paolo Abeni
2026-07-24 9:24 ` [PATCH net-next 1/2] docs: netdev: clarify handling of idle patches Paolo Abeni
2026-07-24 10:22 ` Nicolai Buchwitz
2026-07-24 13:35 ` Matthieu Baerts
2026-07-24 9:24 ` [PATCH net-next 2/2] docs: netdev: clarify expected interactions with LLMs Paolo Abeni
2026-07-24 10:22 ` Nicolai Buchwitz
2026-07-24 11:56 ` Jakub Raczynski
2026-07-24 13:39 ` Matthieu Baerts
2026-07-27 8:24 ` Paolo Abeni
2026-07-27 8:54 ` Matthieu Baerts
2026-08-14 12:47 ` Hangbin Liu
2026-08-14 19:07 ` Jakub Kicinski [this message]
2026-07-28 1:10 ` [PATCH net-next 0/2] docs: netdev: a couple of updates 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=20260814120750.420d75d1@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=j.raczynski@samsung.com \
--cc=liuhangbin@gmail.com \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.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