From: Gleb Natapov <gleb@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] kvm, svm: Fix typo in printk message
Date: Sun, 28 Apr 2013 12:43:33 +0300 [thread overview]
Message-ID: <20130428094333.GE30504@redhat.com> (raw)
In-Reply-To: <1366928521-10073-1-git-send-email-bp@alien8.de>
On Fri, Apr 26, 2013 at 12:22:01AM +0200, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
>
> It is "exit_int_info". It is actually EXITINTINFO in the official docs
> but we don't like screaming docs.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
Applied, thanks.
> ---
> arch/x86/kvm/svm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index a3bba7786ecc..272d29844cc5 100644
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -3491,7 +3491,7 @@ static int handle_exit(struct kvm_vcpu *vcpu)
> exit_code != SVM_EXIT_EXCP_BASE + PF_VECTOR &&
> exit_code != SVM_EXIT_NPF && exit_code != SVM_EXIT_TASK_SWITCH &&
> exit_code != SVM_EXIT_INTR && exit_code != SVM_EXIT_NMI)
> - printk(KERN_ERR "%s: unexpected exit_ini_info 0x%x "
> + printk(KERN_ERR "%s: unexpected exit_int_info 0x%x "
> "exit_code 0x%x\n",
> __func__, svm->vmcb->control.exit_int_info,
> exit_code);
> --
> 1.8.2.135.g7b592fa
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Gleb.
prev parent reply other threads:[~2013-04-28 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 22:22 [PATCH] kvm, svm: Fix typo in printk message Borislav Petkov
2013-04-28 9:43 ` Gleb Natapov [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=20130428094333.GE30504@redhat.com \
--to=gleb@redhat.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.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