From: Jinrong Liang <cloudliang@xxxxxxxxxxx> There is a typo in code comment. Fix it by replacing "Unfortuately" with "Unfortunately". Signed-off-by: Jinrong Liang <cloudliang@xxxxxxxxxxx> --- 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
