From: Shuah Khan <skhan@linuxfoundation.org>
To: Jihed Chaibi <jihed.chaibi.dev@gmail.com>, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH 1/1] Fix typo in cpu-on-off-test selftest script:
Date: Thu, 22 May 2025 16:43:37 -0600 [thread overview]
Message-ID: <a2980c99-6a6e-42ac-8978-8e0ab5319a9c@linuxfoundation.org> (raw)
In-Reply-To: <20250517011928.673585-1-jihed.chaibi.dev@gmail.com>
On 5/16/25 19:19, Jihed Chaibi wrote:
> Fix typo in hotplaggable_offline_cpus function name:
>
> "hotplaggable" is replaced by "hotpluggable"
>
> Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
> ---
Change looks good to me. Change log should specify the
subsusystem. Check submitting patches document and refer
to a few change logs for this file using git log.
Send v2 with a proper change log.
> tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh b/tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh
> index d5dc7e0dc..6232a46ca 100755
> --- a/tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh
> +++ b/tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh
> @@ -67,7 +67,7 @@ hotpluggable_cpus()
> done
> }
>
> -hotplaggable_offline_cpus()
> +hotpluggable_offline_cpus()
> {
> hotpluggable_cpus 0
> }
> @@ -151,7 +151,7 @@ offline_cpu_expect_fail()
>
> online_all_hot_pluggable_cpus()
> {
> - for cpu in `hotplaggable_offline_cpus`; do
> + for cpu in `hotpluggable_offline_cpus`; do
> online_cpu_expect_success $cpu
> done
> }
thanks,
-- Shuah
prev parent reply other threads:[~2025-05-22 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 1:19 [PATCH 1/1] Fix typo in cpu-on-off-test selftest script: Jihed Chaibi
2025-05-22 22:43 ` 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=a2980c99-6a6e-42ac-8978-8e0ab5319a9c@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jihed.chaibi.dev@gmail.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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