From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org, Jani Nikula <jani.nikula@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3 4/4] scripts/kernel-doc: some fixes to kernel-doc comments
Date: Tue, 13 Jan 2026 23:10:36 +0100 [thread overview]
Message-ID: <20260113231036.0b10f4a9@foz.lan> (raw)
In-Reply-To: <20260113224943.3e8b014c@foz.lan>
Em Tue, 13 Jan 2026 22:49:43 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
> Em Tue, 13 Jan 2026 13:55:18 -0700
> Jonathan Corbet <corbet@lwn.net> escreveu:
>
> > Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> >
> > "flowers"? Did the LLM put that out too? :)
Heh, asking it to be funny and use figures of speech gave a funny
yet precise description:
<llm>
There are hidden gremlins and linguistic shadows lurking in the
kernel‑doc.py comments.
Summon them with the aid of an LLM (gpt‑oss 14B), executed locally
like a sorcerer’s spell, using this incantation:
review English grammar and syntax at the comments on the code below:
<cat scripts/kernel-doc.py>
The oracle did not yield a bouquet of roses; instead, it revealed
a handful of wilted blossoms. Gather the radiant ones, and toss
the withered ones into the abyss.
</llm>
If you ever see a patch description like that from my side, you can
be certain that it was a LLM-generated one ;-)
Thanks,
Mauro
next prev parent reply other threads:[~2026-01-13 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 17:19 [PATCH v3 0/4] fix -Werror issues Mauro Carvalho Chehab
2026-01-13 17:19 ` [PATCH v3 1/4] scripts/kernel-doc: fix logic to handle unissued warnings Mauro Carvalho Chehab
2026-01-13 17:19 ` [PATCH v3 2/4] scripts/kernel-doc: avoid error_count overflows Mauro Carvalho Chehab
2026-01-14 6:42 ` Randy Dunlap
2026-01-13 17:19 ` [PATCH v3 3/4] scripts/kernel-doc: ensure that comments are using our coding style Mauro Carvalho Chehab
2026-01-13 17:19 ` [PATCH v3 4/4] scripts/kernel-doc: some fixes to kernel-doc comments Mauro Carvalho Chehab
2026-01-13 20:55 ` Jonathan Corbet
2026-01-13 21:49 ` Mauro Carvalho Chehab
2026-01-13 22:10 ` Mauro Carvalho Chehab [this message]
2026-01-13 22:48 ` OOT: some LLM-generated humor over a patch description - Was: " Mauro Carvalho Chehab
2026-01-13 23:54 ` Jonathan Corbet
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=20260113231036.0b10f4a9@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--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