From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
keyrings@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: [GIT PULL] KEYS changes for v7.3-rc7
Date: Tue, 6 Oct 2026 09:33:35 +0300 [thread overview]
Message-ID: <asSWP-QfvvpjvELc@kernel.org> (raw)
In-Reply-To: <CAHk-=wgXU50=KgZNZc1JDxsSxg9Z+DjG1_2yU-fNXpZtUe4XDw@mail.gmail.com>
On Tue, Oct 06, 2026 at 05:03:42AM +0200, Linus Torvalds wrote:
> On Tue, 6 Oct 2026 at 00:46, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > I've started to take steps towards better quality PRs.
>
> Looks better.
>
> It reads like an llm, but that's perfectly acceptable use of tooling.
> If it was an llm, you can tell it to be a bit less verbose, and that
> it should prefer imperative voice ("Fix it by" vs "The bug was fixed
> by")
Nope, this was not with LLM, honestly :-) I hope it isn't Claude tho
because I can't stand it...
I spent just way too much time fitting all the details while keeping
then compact as possible and that is what I ended up with. And as I
recall saying (I think) previously, I will take a habbit of writing
these at the time when I ack the patch.
I also think that while there are situations where I could use an LLM
for development, using them for PR would impose a quality risk as it is
also the last time to sanity check and drop patches when needed.
Putting things down early and eagerly is probably a right choice and
it is best use of the energy spent on review process.
>
> Linus
Br, Jarkko
next prev parent reply other threads:[~2026-10-06 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 22:46 [GIT PULL] KEYS changes for v7.3-rc7 Jarkko Sakkinen
2026-10-06 3:03 ` Linus Torvalds
2026-10-06 6:33 ` Jarkko Sakkinen [this message]
2026-10-06 3:04 ` pr-tracker-bot
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=asSWP-QfvvpjvELc@kernel.org \
--to=jarkko@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.