From: Lee Jones <lee@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [GIT PULL] LEDs for v6.17
Date: Tue, 5 Aug 2025 14:16:23 +0100 [thread overview]
Message-ID: <20250805131623.GL1049189@google.com> (raw)
In-Reply-To: <CAHk-=whwhtLWi7n1RjOk4Yvmt4sHdEMd9DdzaLdfHc_8StU-qA@mail.gmail.com>
On Thu, 31 Jul 2025, Linus Torvalds wrote:
> Just a small and unimportant nit:
>
> On Wed, 30 Jul 2025 at 08:10, Lee Jones <lee@kernel.org> wrote:
> >
> > * A potential buffer overflow warning in PCA955x was reported by older GCC
> > versions has been fixed by using a more precise format specifier when
> > creating the default LED label.
>
> I'm trying to encourage people to use more straightforward language in
> commit messages, and I ended up rewriting some of yours.
>
> In particular, try to avoid passive voice.
>
> So instead of "A fix has been implemented to Xyz" just say that it
> contains "A fix for Xyz" (or even just "Fix Xyz").
>
> Straight and to the point.
>
> As an example, I edited that "was reported by gcc" and "has been
> fixed", so that bullet point became
>
> - Fix a potential buffer overflow warning in PCA955x reported by
> older GCC versions by using a more precise format specifier when
> creating the default LED label.
>
> in my tree.
>
> This is not a huge deal, I just wanted to point out that "simple and
> to the point" is a good thing, and talking about fixes in some kind of
> passive voice is just strange.
Thanks for fixing.
I'll try to bear it in mind in the future.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-08-05 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 15:10 Lee Jones
2025-07-31 19:05 ` Linus Torvalds
2025-08-05 13:16 ` Lee Jones [this message]
2025-07-31 19:07 ` 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=20250805131623.GL1049189@google.com \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®