mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: fix typos in comments
Date: Fri, 2 Oct 2026 10:40:50 +0200	[thread overview]
Message-ID: <ar9qxmyIZEP2IlMp@orome> (raw)
In-Reply-To: <20260907062107.6859-1-hemanth.selam@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

On Mon, Sep 07, 2026 at 11:51:07AM +0530, Hemanth Selam wrote:
> Fix typos in comments, reported by scripts/checkpatch.pl using the
> misspelling list in scripts/spelling.txt.  Only touches comments, no code
> changes.
> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
>  include/soc/tegra/bpmp-abi.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Applied, thanks. Though honestly this seems like a waste of LLM tokens.
Spell checking is one of those problems that has been solved for a long
time, though obviously we don't consistently run it on the source code,
otherwise we wouldn't still have these typos. Maybe a better use of LLM
tokens would be to have it write a script that can be merged and that
will automatically run a spellcheck on the tree.

For some reason I can't seem to get checkpatch.pl report these spelling
mistakes, so maybe that's part of the reason why these are not flagged
before they get merged?

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-10-02  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  6:21 Hemanth Selam
2026-10-02  8:40 ` Thierry Reding [this message]

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=ar9qxmyIZEP2IlMp@orome \
    --to=thierry.reding@kernel.org \
    --cc=hemanth.selam@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@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

all inboxes | Powered by JetHome®