linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Xiang wangx <wangxiang@cdjrlc.com>, akpm@linux-foundation.org
Cc: shuah@kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] userfaultfd/selftests: Fix typo in comment
Date: Tue, 14 Jun 2022 11:30:05 -0600	[thread overview]
Message-ID: <3e3922c1-c6a7-ac60-2478-6b94defd1ead@linuxfoundation.org> (raw)
In-Reply-To: <20220610071244.59679-1-wangxiang@cdjrlc.com>

On 6/10/22 1:12 AM, Xiang wangx wrote:
> Delete the redundant word 'in'.
> 
> Signed-off-by: Xiang wangx <wangxiang@cdjrlc.com>
> ---
>   tools/testing/selftests/vm/userfaultfd.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c
> index 0bdfc1955229..4bc24581760d 100644
> --- a/tools/testing/selftests/vm/userfaultfd.c
> +++ b/tools/testing/selftests/vm/userfaultfd.c
> @@ -860,7 +860,7 @@ static int stress(struct uffd_stats *uffd_stats)
>   	/*
>   	 * Be strict and immediately zap area_src, the whole area has
>   	 * been transferred already by the background treads. The
> -	 * area_src could then be faulted in in a racy way by still
> +	 * area_src could then be faulted in a racy way by still
>   	 * running uffdio_threads reading zeropages after we zapped
>   	 * area_src (but they're guaranteed to get -EEXIST from
>   	 * UFFDIO_COPY without writing zero pages into area_dst
> 

Thank you. Applied to next Linux 5.20-rc1

thanks,
-- Shuah


      reply	other threads:[~2022-06-14 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  7:12 Xiang wangx
2022-06-14 17:30 ` 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=3e3922c1-c6a7-ac60-2478-6b94defd1ead@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@kernel.org \
    --cc=wangxiang@cdjrlc.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