linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: GuokaiXu <xuguokai@ucas.com.cn>, linux-next@vger.kernel.org
Subject: Re: [PATCH 2/2] tools/testing/selftests:Fixed spelling errors in comments
Date: Thu, 3 Aug 2023 07:00:18 -0700	[thread overview]
Message-ID: <f8262c02-ba63-040b-17e4-d0cb202ce7f5@infradead.org> (raw)
In-Reply-To: <803778AC500E556D+20230803060557.GA6671@xgk8823>



On 8/2/23 23:05, GuokaiXu wrote:
> From 844784381c30373524346d342003952aeec73a16 Mon Sep 17 00:00:00 2001
> From: GuokaiXu <xuguokai@ucas.com.cn>
> Date: Thu, 3 Aug 2023 13:26:59 +0800
> Subject: [PATCH 2/2] Fixed some spelling errors in comments.
> 
> Signed-off-by: GuokaiXu <xuguokai@ucas.com.cn>
> ---
>  tools/testing/selftests/arm64/pauth/pac.c              | 2 +-
>  tools/testing/selftests/bpf/progs/test_subprogs.c      | 2 +-
>  tools/testing/selftests/sync/sync_stress_parallelism.c | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/testing/selftests/arm64/pauth/pac.c b/tools/testing/selftests/arm64/pauth/pac.c
> index b743daa772f5..b236d181feef 100644
> --- a/tools/testing/selftests/arm64/pauth/pac.c
> +++ b/tools/testing/selftests/arm64/pauth/pac.c
> @@ -289,7 +289,7 @@ TEST(single_thread_different_keys)
>  
>  /*
>   * fork() does not change keys. Only exec() does so call a worker program.
> - * Its only job is to sign a value and report back the resutls
> + * Its only job is to sign a value and report back the results
>   */
>  TEST(exec_changed_keys)
>  {
> diff --git a/tools/testing/selftests/bpf/progs/test_subprogs.c b/tools/testing/selftests/bpf/progs/test_subprogs.c
> index a8d602d7c88a..ad68697c3c91 100644
> --- a/tools/testing/selftests/bpf/progs/test_subprogs.c
> +++ b/tools/testing/selftests/bpf/progs/test_subprogs.c
> @@ -39,7 +39,7 @@ static __noinline int sub4(int w)
>  	return w + sub3(5) + sub1(6);
>  }
>  
> -/* sub5() is an identitify function, just to test weirder functions layout and
> +/* sub5() is an identify function, just to test weirder functions layout and

                   identity
maybe. I think. maybe.

>   * call patterns
>   */
>  static __noinline int sub5(int v)
> diff --git a/tools/testing/selftests/sync/sync_stress_parallelism.c b/tools/testing/selftests/sync/sync_stress_parallelism.c
> index e6c9be671dfc..6ce56ca204c4 100644
> --- a/tools/testing/selftests/sync/sync_stress_parallelism.c
> +++ b/tools/testing/selftests/sync/sync_stress_parallelism.c
> @@ -87,7 +87,7 @@ int test_stress_two_threads_shared_timeline(void)
>  
>  	/*
>  	 * Use a single timeline to synchronize two threads
> -	 * hammmering on the same counter.
> +	 * hammering on the same counter.
>  	 */
>  
>  	pthread_create(&a, NULL, (void *(*)(void *))

-- 
~Randy

      reply	other threads:[~2023-08-03 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  6:05 [PATCH 2/2] tools/testing/selftests:Fixed spelling errors in comments GuokaiXu
2023-08-03 14:00 ` Randy Dunlap [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=f8262c02-ba63-040b-17e4-d0cb202ce7f5@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=xuguokai@ucas.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).