All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Thomas Gleixner <tglx@kernel.org>,
	 "Artem B. Bityuckiy" <dedekind@infradead.org>,
	 linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: stop BBT creation when the marker scan fails
Date: Thu, 19 Nov 2026 11:18:52 +0100	[thread overview]
Message-ID: <87tslddsz7.fsf@bootlin.com> (raw)
In-Reply-To: <CADvTj4ok=HXZiD4t1pgomZAD5_zRpe3uJyRgfBiPON6Rfx-wVA@mail.gmail.com> (James Hilliard's message of "Thu, 19 Nov 2026 02:35:26 -0700")


>> >> I would prefer if you could write your own commit logs, giving us more
>> >> confidence on the work that has been asked. You can use an LLM to
>> >> improve/enhance it obviously.
>> >
>> > To be honest I've never been great at writing commit messages in
>> > general and have gotten a lot more complaints about commit messages
>> > missing important details prior to using LLM's. I can barely tell the
>>
>> For me the code is getting better but the commit logs are unclear. Some
>> details which don't need (imo) to be written are there, and the big
>> picture is often missing or not clearly stated before the details.
>>
>> Don't get me wrong, using an LLM to refine/reword/reorganize is fine,
>> but letting the LLM write it entirely is not working well.
>
> I guess the issue is that I often don't have the best understanding
> of what the big picture that needs explanation in the commit messages
> is some of the time, if I did then I would then just instruct the LLM to
> make those edits whenever I review patches before sending them.
>
> I think I just don't have good intuition when it comes to predicting what is
> important to explain in commit messages.

I get it, but for someone submitting this many patches, that lack of
understanding is precisely the problem: delegating the wording to an LLM
when you don't know the rationale doesn't remove the cost, it just
shifts it onto others.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Thomas Gleixner <tglx@kernel.org>,
	 "Artem B. Bityuckiy" <dedekind@infradead.org>,
	 linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: stop BBT creation when the marker scan fails
Date: Thu, 19 Nov 2026 11:18:52 +0100	[thread overview]
Message-ID: <87tslddsz7.fsf@bootlin.com> (raw)
In-Reply-To: <CADvTj4ok=HXZiD4t1pgomZAD5_zRpe3uJyRgfBiPON6Rfx-wVA@mail.gmail.com> (James Hilliard's message of "Thu, 19 Nov 2026 02:35:26 -0700")


>> >> I would prefer if you could write your own commit logs, giving us more
>> >> confidence on the work that has been asked. You can use an LLM to
>> >> improve/enhance it obviously.
>> >
>> > To be honest I've never been great at writing commit messages in
>> > general and have gotten a lot more complaints about commit messages
>> > missing important details prior to using LLM's. I can barely tell the
>>
>> For me the code is getting better but the commit logs are unclear. Some
>> details which don't need (imo) to be written are there, and the big
>> picture is often missing or not clearly stated before the details.
>>
>> Don't get me wrong, using an LLM to refine/reword/reorganize is fine,
>> but letting the LLM write it entirely is not working well.
>
> I guess the issue is that I often don't have the best understanding
> of what the big picture that needs explanation in the commit messages
> is some of the time, if I did then I would then just instruct the LLM to
> make those edits whenever I review patches before sending them.
>
> I think I just don't have good intuition when it comes to predicting what is
> important to explain in commit messages.

I get it, but for someone submitting this many patches, that lack of
understanding is precisely the problem: delegating the wording to an LLM
when you don't know the rationale doesn't remove the cost, it just
shifts it onto others.

  reply	other threads:[~2026-11-19 10:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  5:52 [PATCH] mtd: rawnand: stop BBT creation when the marker scan fails James Hilliard
2026-11-04  5:52 ` James Hilliard
2026-11-18  9:45 ` Miquel Raynal
2026-11-18  9:45   ` Miquel Raynal
2026-11-18 19:11   ` James Hilliard
2026-11-18 19:11     ` James Hilliard
2026-11-19  8:38     ` Miquel Raynal
2026-11-19  8:38       ` Miquel Raynal
2026-11-19  9:35       ` James Hilliard
2026-11-19  9:35         ` James Hilliard
2026-11-19 10:18         ` Miquel Raynal [this message]
2026-11-19 10:18           ` Miquel Raynal
2026-11-19 10:40           ` James Hilliard
2026-11-19 10:40             ` James Hilliard

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=87tslddsz7.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=dedekind@infradead.org \
    --cc=james.hilliard1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=tglx@kernel.org \
    --cc=vigneshr@ti.com \
    /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.