From: Hemanth Selam <hemanth.selam@gmail.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
"John B. Wyatt IV" <jwyatt@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpupower: fix typos in comments
Date: Mon, 7 Sep 2026 10:09:33 +0530 [thread overview]
Message-ID: <20260907043933.33452-4-hemanth.selam@gmail.com> (raw)
In-Reply-To: <f1b5ae1c-f6cd-4f9f-9143-4bdd3b8c2b46@linuxfoundation.org>
Fair question, and the honest answer is that I did not need it for the
typos themselves.
checkpatch and codespell found every word in this series. What the
assistant did was the work around that: splitting several hundred one-line
fixes into per-subsystem patches, running get_maintainer.pl to decide who
each one goes to, and drafting the changelogs. No part of the diff was
model-generated - each change is the substitution checkpatch printed.
The Assisted-by: tag names the tool and model because
Documentation/process/coding-assistants.rst asks for the tool to be
identified, and the prevailing form in the tree is Vendor:model.
I should add that the review this series has had since Friday has turned up
cases where the mechanical fix was simply wrong - deleting a word from
"kicks in in a timely manner", for instance. I am auditing the rest and
withdrawing the bad ones rather than leaving them for maintainers to catch.
prev parent reply other threads:[~2026-09-07 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 12:40 [PATCH] cpupower: fix typos in comments Hemanth Selam
2026-09-04 17:31 ` Shuah Khan
2026-09-07 4:39 ` Hemanth Selam [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=20260907043933.33452-4-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=trenn@suse.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