From: Alison Schofield <alison.schofield@intel.com>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Dan Williams <djbw@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>, Ira Weiny <iweiny@kernel.org>,
<nvdimm@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] nvdimm: fix typos and repeated words in comments
Date: Thu, 15 Oct 2026 18:29:31 -0700 [thread overview]
Message-ID: <atF9-7CD_XRiUH4v@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260907063434.23060-1-hemanth.selam@gmail.com>
On Mon, Sep 07, 2026 at 12:04:32PM +0530, Hemanth Selam wrote:
> 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.
This one is a NAK
Not going to churn for non user visible typos.
>
> Hemanth Selam (2):
> nvdimm: fix typos in comments
> tools/testing: fix repeated word 'from' in comment
>
> drivers/nvdimm/namespace_devs.c | 2 +-
> include/linux/libnvdimm.h | 2 +-
> tools/testing/nvdimm/test/nfit.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> --
> 2.48.1
>
prev parent reply other threads:[~2026-10-16 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:34 Hemanth Selam
2026-09-07 6:34 ` [PATCH 1/2] nvdimm: fix typos " Hemanth Selam
2026-09-07 6:34 ` [PATCH 2/2] tools/testing: fix repeated word 'from' in comment Hemanth Selam
2026-10-16 1:29 ` Alison Schofield [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=atF9-7CD_XRiUH4v@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=djbw@kernel.org \
--cc=hemanth.selam@gmail.com \
--cc=iweiny@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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 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®