From: Jarkko Sakkinen <jarkko@kernel.org>
To: keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: AI assisted patches and credits where it is due
Date: Tue, 14 Jul 2026 00:29:42 +0300 [thread overview]
Message-ID: <alVYxv8esyv2SKpt@kernel.org> (raw)
I sometimes get patches, which are literally just LLM output dumps.
Even finding out if there is a bug symptom/bug has been delegated to
me.
I'm thinking of followning process when this happens next time:
1. Do all the real work.
2. Retain whatever model was used as co-author.
3. Downgrade submitted from author to reporter.
I've seen also reasonable AI assisted patches and this type of behavior
just downplays them.
Any better ideas? I'm open.
BR, Jarkko
reply other threads:[~2026-07-13 21:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alVYxv8esyv2SKpt@kernel.org \
--to=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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