From: Shuah Khan <skhan@linuxfoundation.org>
To: Colin Ian King <colin.i.king@gmail.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH][next] selftests: sched: Fix spelling mistake "hiearchy" -> "hierarchy"
Date: Tue, 20 Feb 2024 17:24:34 -0700 [thread overview]
Message-ID: <ab3e1d41-f3e7-406c-8de5-426bcd2ba602@linuxfoundation.org> (raw)
In-Reply-To: <20240220092323.2677156-1-colin.i.king@gmail.com>
On 2/20/24 02:23, Colin Ian King wrote:
> There is a spelling mistake in a printed message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> tools/testing/selftests/sched/cs_prctl_test.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/sched/cs_prctl_test.c b/tools/testing/selftests/sched/cs_prctl_test.c
> index 7ba057154343..62fba7356af2 100644
> --- a/tools/testing/selftests/sched/cs_prctl_test.c
> +++ b/tools/testing/selftests/sched/cs_prctl_test.c
> @@ -276,7 +276,7 @@ int main(int argc, char *argv[])
> if (setpgid(0, 0) != 0)
> handle_error("process group");
>
> - printf("\n## Create a thread/process/process group hiearchy\n");
> + printf("\n## Create a thread/process/process group hierarchy\n");
> create_processes(num_processes, num_threads, procs);
> need_cleanup = 1;
> disp_processes(num_processes, procs);
Applied to linux-kselftest next for Linux 6.9-rc1
thanks,
-- Shuah
next prev parent reply other threads:[~2024-02-21 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 9:23 [PATCH][next] selftests: sched: Fix spelling mistake "hiearchy" -> "hierarchy" Colin Ian King
2024-02-21 0:24 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-27 8:42 Colin Ian King
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=ab3e1d41-f3e7-406c-8de5-426bcd2ba602@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--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