From: Shuah Khan <skhan@linuxfoundation.org>
To: Hemanth Selam <hemanth.selam@gmail.com>,
Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
"John B. Wyatt IV" <jwyatt@redhat.com>,
John Kacur <jkacur@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] cpupower: fix typos in comments
Date: Fri, 4 Sep 2026 11:31:13 -0600 [thread overview]
Message-ID: <f1b5ae1c-f6cd-4f9f-9143-4bdd3b8c2b46@linuxfoundation.org> (raw)
In-Reply-To: <20260904124005.3270-1-hemanth.selam@gmail.com>
On 9/4/26 06:40, 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
Why do you need AI assistance to fix typos found by checkpatch.pl?
How did Cursor:claude-opus-5 assist you?
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
> tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c | 4 ++--
> tools/power/cpupower/utils/idle_monitor/mperf_monitor.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c b/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c
> index e8b3841d5c0f..b15371e3e6bd 100644
> --- a/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c
> +++ b/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c
> @@ -72,7 +72,7 @@ void print_n_spaces(int n)
> }
>
> /*s is filled with left and right spaces
> - *to make its length atleast n+1
> + *to make its length at least n+1
> */
> int fill_string_with_spaces(char *s, int n)
> {
> @@ -263,7 +263,7 @@ static void parse_monitor_param(char *param)
> "try -l option\n"), param);
> exit(EXIT_FAILURE);
> }
> - /* Override detected/registerd monitors array with requested one */
> + /* Override detected/registered monitors array with requested one */
> memcpy(monitors, tmp_mons,
> sizeof(struct cpuidle_monitor *) * MONITORS_MAX);
> avail_monitors = hits;
> diff --git a/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c b/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c
> index 5ae02c3d5b64..62b8cfb02040 100644
> --- a/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c
> +++ b/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c
> @@ -276,7 +276,7 @@ static int init_maxfreq_mode(void)
> cpupower_cpu_info.vendor == X86_VENDOR_HYGON) {
> /* MSR_AMD_HWCR tells us whether TSC runs at P0/mperf
> * freq.
> - * A test whether hwcr is accessable/available would be:
> + * A test whether hwcr is accessible/available would be:
> * (cpupower_cpu_info.family > 0x10 ||
> * cpupower_cpu_info.family == 0x10 &&
> * cpupower_cpu_info.model >= 0x2))
thanks,
-- Shuah
prev parent reply other threads:[~2026-09-04 17:31 UTC|newest]
Thread overview: 2+ 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 [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=f1b5ae1c-f6cd-4f9f-9143-4bdd3b8c2b46@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=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=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