From: Like Xu <like.xu.linux@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org,
Sean Christopherson <sean.j.christopherson@intel.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] kvm: minor fixes and cleanups
Date: Wed, 6 Apr 2022 14:37:11 +0800 [thread overview]
Message-ID: <20220406063715.55625-1-likexu@tencent.com> (raw)
Another new kernel cycle starts ticking and my bot seems to have some
complaints about some new changes. Please check if any of them helps.
Like Xu (4):
KVM: x86/xen: Remove the redundantly included header file lapic.h
selftests: kvm: add tsc_scaling_sync to .gitignore
selftests: kvm/x86/xen: Replace a comma in the xen_shinfo_test with
semicolon
Documentation: KVM: Add SPDX-License-Identifier tag
Documentation/virt/kvm/vcpu-requests.rst | 2 ++
Documentation/virt/kvm/x86/amd-memory-encryption.rst | 2 ++
Documentation/virt/kvm/x86/errata.rst | 2 +-
Documentation/virt/kvm/x86/running-nested-guests.rst | 2 ++
arch/x86/kvm/xen.c | 1 -
tools/testing/selftests/kvm/.gitignore | 1 +
tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c | 2 +-
7 files changed, 9 insertions(+), 3 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-06 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 6:37 Like Xu [this message]
2022-04-06 6:37 ` [PATCH 1/4] KVM: x86/xen: Remove the redundantly included header file lapic.h Like Xu
2022-04-06 6:37 ` [PATCH 2/4] selftests: kvm: add tsc_scaling_sync to .gitignore Like Xu
2022-04-06 6:37 ` [PATCH 3/4] selftests: kvm/x86/xen: Replace a comma in the xen_shinfo_test with semicolon Like Xu
2022-04-06 6:37 ` [PATCH 4/4] Documentation: KVM: Add SPDX-License-Identifier tag Like Xu
2022-04-08 16:37 ` [PATCH 0/4] kvm: minor fixes and cleanups Paolo Bonzini
2022-04-09 2:12 ` Like Xu
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=20220406063715.55625-1-likexu@tencent.com \
--to=like.xu.linux@gmail.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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
all inboxes | Powered by JetHome®