* [PATCH] KVM: x86: Fix spelling mistake "Unfortuately" -> "Unfortunately"
@ 2022-01-19 13:13 Jinrong Liang
0 siblings, 0 replies; only message in thread
From: Jinrong Liang @ 2022-01-19 13:13 UTC (permalink / raw)
To: Paolo Bonzini
Cc: Wanpeng Li, Sean Christopherson, Jim Mattson, Vitaly Kuznetsov,
Joerg Roedel, Jinrong Liang, kvm, linux-kernel
From: Jinrong Liang <cloudliang@tencent.com>
There is a typo in code comment. Fix it by replacing "Unfortuately"
with "Unfortunately".
Signed-off-by: Jinrong Liang <cloudliang@tencent.com>
---
arch/x86/kvm/svm/svm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
index 6d31d357a83b..0207bd385a76 100644
--- a/arch/x86/kvm/svm/svm.c
+++ b/arch/x86/kvm/svm/svm.c
@@ -1913,7 +1913,7 @@ static int shutdown_interception(struct kvm_vcpu *vcpu)
/*
* VMCB is undefined after a SHUTDOWN intercept. INIT the vCPU to put
- * the VMCB in a known good state. Unfortuately, KVM doesn't have
+ * the VMCB in a known good state. Unfortunately, KVM doesn't have
* KVM_MP_STATE_SHUTDOWN and can't add it without potentially breaking
* userspace. At a platform view, INIT is acceptable behavior as
* there exist bare metal platforms that automatically INIT the CPU
--
2.27.0
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-01-19 13:15 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-19 13:13 [PATCH] KVM: x86: Fix spelling mistake "Unfortuately" -> "Unfortunately" Jinrong Liang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®