From: SJ Park <sj@kernel.org>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>,
David Hildenbrand <david@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/5] asm-generic: fix typo "explicity" in comment
Date: Fri, 4 Sep 2026 16:59:15 -0700 [thread overview]
Message-ID: <20260904235916.67459-1-sj@kernel.org> (raw)
In-Reply-To: <20260904104854.25272-2-hemanth.selam@gmail.com>
On Fri, 4 Sep 2026 16:18:46 +0530 Hemanth Selam <hemanth.selam@gmail.com> wrote:
> Correct "explicity" to "Explicitly", reported by scripts/checkpatch.pl
Too trivial, but 's/explicity/Explicity/'
> using the misspelling list in scripts/spelling.txt.
Again, too trivial, but I think mentioning spelling.txt is not necessary. LLMs
might disagree.
> Only touches comments,
> no code changes.
Anyway good catch, and looks correct to me. Thank you for fixing this.
>
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
Reviewed-by: SJ Park <sj@kernel.org>
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-09-04 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 10:48 [PATCH 0/5] asm-generic: fix typos in comments Hemanth Selam
2026-09-04 10:48 ` [PATCH 1/5] asm-generic: fix typo "explicity" in comment Hemanth Selam
2026-09-04 11:33 ` Lorenzo Stoakes (ARM)
2026-09-04 21:58 ` Randy Dunlap
2026-09-04 23:59 ` SJ Park [this message]
2026-09-04 10:48 ` [PATCH 2/5] char: fix typo "funcion" " Hemanth Selam
2026-09-04 11:34 ` Lorenzo Stoakes (ARM)
2026-09-04 10:48 ` [PATCH 3/5] lib: fix typos in comments Hemanth Selam
2026-09-04 10:48 ` [PATCH 4/5] mm: fix typo "mergable" in comment Hemanth Selam
2026-09-04 11:35 ` Lorenzo Stoakes (ARM)
2026-09-04 10:48 ` [PATCH 5/5] tools/testing: " Hemanth Selam
2026-09-04 11:37 ` Lorenzo Stoakes (ARM)
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=20260904235916.67459-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=david@kernel.org \
--cc=hemanth.selam@gmail.com \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=vbabka@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®