From: Marcelo Tosatti <mtosatti@redhat.com>
To: Guo Chao <yan@linux.vnet.ibm.com>
Cc: avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 2/2] [TRIVIAL]KVM: fix a typo in comment
Date: Wed, 27 Jun 2012 22:00:54 -0300 [thread overview]
Message-ID: <20120628010054.GB18388@amt.cnet> (raw)
In-Reply-To: <1339731271.5594.6.camel@yanx>
On Fri, Jun 15, 2012 at 11:34:31AM +0800, Guo Chao wrote:
>
> Signed-off-by: Guo Chao <yan@linux.vnet.ibm.com>
> ---
> arch/x86/kvm/vmx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index f48cef3..7593693 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -5880,7 +5880,7 @@ static int vmx_handle_exit(struct kvm_vcpu *vcpu)
> return handle_invalid_guest_state(vcpu);
>
> /*
> - * the KVM_REQ_EVENT optimization bit is only on for one entry, and if
> + * The KVM_REQ_EVENT optimization bit is only on for one entry, and if
> * we did not inject a still-pending event to L1 now because of
> * nested_run_pending, we need to re-enable this bit.
> */
There is no rule about comments in code starting with uppercase.
Patches to correct spelling would be accepted.
prev parent reply other threads:[~2012-06-28 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 3:34 [PATCH 2/2] [TRIVIAL]KVM: fix a typo in comment Guo Chao
2012-06-28 1:00 ` Marcelo Tosatti [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=20120628010054.GB18388@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yan@linux.vnet.ibm.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