All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: Wang Qing <wangqing@vivo.com>
Cc: Shuah Khan <shuah@kernel.org>, Peter Xu <peterx@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Joe Perches <joe@perches.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tool: selftests: fix spelling typo of 'writting'
Date: Sat, 7 Nov 2020 12:44:52 +0200	[thread overview]
Message-ID: <20201107104452.GF301789@linux.ibm.com> (raw)
In-Reply-To: <1604740776-27082-1-git-send-email-wangqing@vivo.com>

On Sat, Nov 07, 2020 at 05:19:35PM +0800, Wang Qing wrote:
> writting -> writing
> 
> Signed-off-by: Wang Qing <wangqing@vivo.com>

Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>

> ---
>  tools/testing/selftests/vm/userfaultfd.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c
> index 9b0912a..9132fae7
> --- a/tools/testing/selftests/vm/userfaultfd.c
> +++ b/tools/testing/selftests/vm/userfaultfd.c
> @@ -894,7 +894,7 @@ static int faulting_process(int signal_test)
>  				count_verify[nr]);
>  	        }
>  		/*
> -		 * Trigger write protection if there is by writting
> +		 * Trigger write protection if there is by writing
>  		 * the same value back.
>  		 */
>  		*area_count(area_dst, nr) = count;
> @@ -922,7 +922,7 @@ static int faulting_process(int signal_test)
>  				count_verify[nr]); exit(1);
>  		}
>  		/*
> -		 * Trigger write protection if there is by writting
> +		 * Trigger write protection if there is by writing
>  		 * the same value back.
>  		 */
>  		*area_count(area_dst, nr) = count;
> -- 
> 2.7.4
> 

-- 
Sincerely yours,
Mike.

      reply	other threads:[~2020-11-07 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-07  9:19 [PATCH] tool: selftests: fix spelling typo of 'writting' Wang Qing
2020-11-07 10:44 ` Mike Rapoport [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=20201107104452.GF301789@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=peterx@redhat.com \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=shuah@kernel.org \
    --cc=wangqing@vivo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.