From: Hemanth Selam <hemanth.selam@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] md: fix typos and repeated words in comments
Date: Fri, 4 Sep 2026 18:18:20 +0530 [thread overview]
Message-ID: <20260904124824.9585-1-hemanth.selam@gmail.com> (raw)
This corrects 2 misspellings and repeated words in comments. Each is a
separate patch so that any one of them can be dropped without touching
the rest.
Nothing outside comments changes. Every touched C file was checked by
dropping its comments, replacing each string literal with a placeholder
and collapsing whitespace; what remained was identical before and after,
so the compiled code cannot differ.
The mistakes were found with scripts/checkpatch.pl against the list in
scripts/spelling.txt. The scanning, the edits and the changelogs were
produced with Cursor running the claude-opus-5 model, from a request to
find and fix spelling mistakes across the tree, and every correction was
then re-checked by the comparison described above. Words that name an
identifier were left alone deliberately, even when they read as typos,
because correcting the prose would make the comment disagree with the
code it describes.
Tested by building x86_64 defconfig at v7.3-rc1-269-gbc35965f6940, which
is clean. Nothing else was built, so any patch touching code that
x86_64 defconfig does not compile has been read but not compiled.
Hemanth Selam (2):
md: fix typos in comments
lib: fix repeated word 'the' in comment
drivers/md/raid1-10.c | 2 +-
drivers/md/raid10.c | 2 +-
lib/raid/raid6/algos.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.48.1
next reply other threads:[~2026-09-04 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 12:48 Hemanth Selam [this message]
2026-09-04 12:48 ` [PATCH 1/2] md: fix typos " Hemanth Selam
2026-09-04 12:48 ` [PATCH 2/2] lib: fix repeated word 'the' in comment Hemanth Selam
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=20260904124824.9585-1-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--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
all inboxes | Powered by JetHome®