From: Michael Ellerman <mpe@ellerman.id.au>
To: wangjianli <wangjianli@cdjrlc.com>,
benh@kernel.crashing.org, paulus@samba.org,
Julia.Lawall@inria.fr, liubo03@inspur.com
Cc: wangjianli <wangjianli@cdjrlc.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/kvm: fix repeated words in comments Delete the redundant word 'that'.
Date: Mon, 25 Jul 2022 16:51:19 +1000 [thread overview]
Message-ID: <87bktdd6s8.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220724062920.1551-1-wangjianli@cdjrlc.com>
wangjianli <wangjianli@cdjrlc.com> writes:
> Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
> ---
> arch/powerpc/kvm/book3s_64_mmu_hv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kvm/book3s_64_mmu_hv.c b/arch/powerpc/kvm/book3s_64_mmu_hv.c
> index 514fd45c1994..73c6db20cd8a 100644
> --- a/arch/powerpc/kvm/book3s_64_mmu_hv.c
> +++ b/arch/powerpc/kvm/book3s_64_mmu_hv.c
> @@ -1601,7 +1601,7 @@ long kvm_vm_ioctl_resize_hpt_commit(struct kvm *kvm,
> * is valid, it is written to the HPT as if an H_ENTER with the
> * exact flag set was done. When the invalid count is non-zero
> * in the header written to the stream, the kernel will make
> - * sure that that many HPTEs are invalid, and invalidate them
> + * sure that many HPTEs are invalid, and invalidate them
> * if not.
The existing wording is correct:
"the kernel will make sure that ... that many HPTEs are invalid"
cheers
next prev parent reply other threads:[~2022-07-25 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 6:29 [PATCH] powerpc/kvm: fix repeated words in comments Delete the redundant word 'that' wangjianli
2022-07-25 6:51 ` Michael Ellerman [this message]
2022-07-25 7:14 ` Julia Lawall
2022-07-25 10:35 ` Michael Ellerman
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=87bktdd6s8.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Julia.Lawall@inria.fr \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liubo03@inspur.com \
--cc=paulus@samba.org \
--cc=wangjianli@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