From: linmiaohe <linmiaohe@huawei.com>
To: <pbonzini@redhat.com>, <rkrcmar@redhat.com>,
<sean.j.christopherson@intel.com>, <vkuznets@redhat.com>,
<wanpengli@tencent.com>, <jmattson@google.com>, <joro@8bytes.org>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<hpa@zytor.com>
Cc: <linmiaohe@huawei.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>
Subject: [PATCH v2 0/4] Fix various comment errors
Date: Thu, 12 Dec 2019 16:18:34 +0800 [thread overview]
Message-ID: <1576138718-32728-1-git-send-email-linmiaohe@huawei.com> (raw)
From: Miaohe Lin <linmiaohe@huawei.com>
Fix various comment mistakes, such as typo, grammar mistake, out-dated
function name, writing error and so on. It is a bit tedious and many
thanks for review in advance.
---
v2:
Fix some comments according to Sean' advice and do the patch reorganizing.
Miaohe Lin (4):
KVM: VMX: Fix some typos and out-dated function names in comments
KVM: x86: Fix some comment typos and grammar mistakes
KVM: Fix some writing mistakes and wrong function name in comments
KVM: hyperv: Fix some typos in vcpu unimpl info
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/hyperv.c | 6 +++---
arch/x86/kvm/ioapic.c | 2 +-
arch/x86/kvm/lapic.c | 4 ++--
arch/x86/kvm/vmx/nested.c | 2 +-
arch/x86/kvm/vmx/vmcs_shadow_fields.h | 4 ++--
arch/x86/kvm/vmx/vmx.c | 8 ++++----
virt/kvm/kvm_main.c | 6 +++---
8 files changed, 17 insertions(+), 17 deletions(-)
--
2.19.1
next reply other threads:[~2019-12-12 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 8:18 linmiaohe [this message]
2019-12-12 8:18 ` [PATCH v2 1/4] KVM: VMX: Fix some typos and out-dated function names in comments linmiaohe
2019-12-12 8:18 ` [PATCH v2 2/4] KVM: x86: Fix some comment typos and grammar mistakes linmiaohe
2019-12-12 8:18 ` [PATCH v2 3/4] KVM: Fix some writing mistakes and wrong function name in comments linmiaohe
2019-12-12 8:18 ` [PATCH v2 4/4] KVM: hyperv: Fix some typos in vcpu unimpl info linmiaohe
2019-12-12 9:20 ` 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=1576138718-32728-1-git-send-email-linmiaohe@huawei.com \
--to=linmiaohe@huawei.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.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
all inboxes | Powered by JetHome®