From: Sasha Levin <sashal@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Dan Williams <dan.j.williams@intel.com>,
Theodore Ts'o <tytso@mit.edu>, Jonathan Corbet <corbet@lwn.net>,
Kees Cook <kees@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] Documentation: Provide guidelines for kernel development tools
Date: Tue, 28 Oct 2025 13:42:50 -0400 [thread overview]
Message-ID: <aQEAms7uBHLwiRJE@laps> (raw)
In-Reply-To: <CANiq72k7LQwXFnZgh8fCLNnx=v17Yb7yVcPQT_cdPi5k=17jbA@mail.gmail.com>
On Tue, Oct 28, 2025 at 04:29:14PM +0100, Miguel Ojeda wrote:
>On Mon, Oct 27, 2025 at 9:13 PM Dave Hansen <dave.hansen@linux.intel.com> wrote:
>> + - ChatGPT generated a new function in your patch to sort list entries.
>> + - A .c file in the patch was originally generated by Gemini but cleaned
>> + up by hand.
>
>Like Jon, it also crossed my mind using just LLM here or perhaps
>mentioning "open" models. On the other hand, it is clear commercial
>models are getting used already, e.g. Gemini is in the commit log
>already and Claude is in the mailing list.
I *think* that this was based on the experience[1] Kees had with LLMs, and my
thoughts were that this example would match what a developer were to write if
they were asked to document the usage of tooling.
And yes, we shouldn't mention proprietary brand names in kernel docs, so I
fully agree with Jon and Miguel here. We should however encourage contributors
to list the actual tools/LLMs they used, as this could be interesting down the
road...
[1] https://hachyderm.io/@kees/114907228284590439
--
Thanks,
Sasha
prev parent reply other threads:[~2025-10-28 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 20:12 [PATCH] Documentation: Provide guidelines for kernel development tools Dave Hansen
2025-10-27 20:48 ` Jonathan Corbet
2025-10-28 15:29 ` Miguel Ojeda
2025-10-28 17:42 ` Sasha Levin [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=aQEAms7uBHLwiRJE@laps \
--to=sashal@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tytso@mit.edu \
/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.