From: Ingo Molnar <mingo@kernel.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: pbonzini@redhat.com, seanjc@google.com, vkuznets@redhat.com,
wanpengli@tencent.com, jmattson@google.com, joro@8bytes.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, hpa@zytor.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH V2] KVM: x86: A typo fix
Date: Mon, 22 Mar 2021 21:16:44 +0100 [thread overview]
Message-ID: <20210322201644.GA1955593@gmail.com> (raw)
In-Reply-To: <20210322060409.2605006-1-unixbhaskar@gmail.com>
* Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
> s/resued/reused/
>
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> Changes from V1:
> As Ingo found the correct word for replacement, so incorporating.
>
> arch/x86/include/asm/kvm_host.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
> index 3768819693e5..e37c2ebc02e5 100644
> --- a/arch/x86/include/asm/kvm_host.h
> +++ b/arch/x86/include/asm/kvm_host.h
> @@ -1488,7 +1488,7 @@ extern u64 kvm_mce_cap_supported;
> /*
> * EMULTYPE_NO_DECODE - Set when re-emulating an instruction (after completing
> * userspace I/O) to indicate that the emulation context
> - * should be resued as is, i.e. skip initialization of
> + * should be reused as is, i.e. skip initialization of
> * emulation context, instruction fetch and decode.
> *
> * EMULTYPE_TRAP_UD - Set when emulating an intercepted #UD from hardware.
I already fixed this typo - and another 185 typos, in this
comprehensive cleanup of arch/x86/ typos in tip:x86/cleanups:
d9f6e12fb0b7: ("x86: Fix various typos in comments")
163b099146b8: ("x86: Fix various typos in comments, take #2")
Please check future typo fixes against tip:master.
Thanks,
Ingo
next prev parent reply other threads:[~2021-03-22 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 6:04 [PATCH V2] KVM: x86: A typo fix Bhaskar Chowdhury
2021-03-22 20:16 ` Ingo Molnar [this message]
2021-03-22 20:21 ` Bhaskar Chowdhury
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=20210322201644.GA1955593@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=unixbhaskar@gmail.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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