From: Sean Christopherson <sean.j.christopherson@intel.com>
To: linmiaohe <linmiaohe@huawei.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"jmattson@google.com" <jmattson@google.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [PATCH] KVM: Fix some obsolete comments
Date: Wed, 26 Feb 2020 07:30:35 -0800 [thread overview]
Message-ID: <20200226153035.GB9940@linux.intel.com> (raw)
In-Reply-To: <3e25a121a6754020ac3a1eda9fb7fad6@huawei.com>
On Wed, Feb 26, 2020 at 01:48:28AM +0000, linmiaohe wrote:
> Vitaly Kuznetsov <vkuznets@redhat.com> writes:
> >linmiaohe <linmiaohe@huawei.com> writes:
> >> throws
> >> - * #UD or #GP.
> >> + * #UD, #GP or #SS.
> >
> >Oxford comma, anyone? :-)))
>
> I have no strong preference. ^_^
I'm also a fan of the Oxford comma when it comes to describing code.
next prev parent reply other threads:[~2020-02-26 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 1:48 [PATCH] KVM: Fix some obsolete comments linmiaohe
2020-02-26 15:30 ` Sean Christopherson [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-27 1:35 linmiaohe
2020-02-25 3:05 linmiaohe
2020-02-25 13:04 ` Vitaly Kuznetsov
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=20200226153035.GB9940@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).