From: Sean Christopherson <seanjc@google.com>
To: pbonzini@redhat.com, kvm@vger.kernel.org,
Kai Huang <kai.huang@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fixup two comments
Date: Fri, 1 Nov 2024 12:25:56 -0700 [thread overview]
Message-ID: <ZyUrRP7sa3IqsVwP@google.com> (raw)
In-Reply-To: <173039499504.1507535.6500285672510733682.b4-ty@google.com>
On Thu, Oct 31, 2024, Sean Christopherson wrote:
> On Tue, 08 Oct 2024 23:45:12 +1300, Kai Huang wrote:
> > Spotted two nit issues in two comments of the apicv code (if I got it
> > right) which probably are worth fixing.
> >
> > Kai Huang (2):
> > KVM: x86: Fix a comment inside kvm_vcpu_update_apicv()
> > KVM: x86: Fix a comment inside __kvm_set_or_clear_apicv_inhibit()
> >
> > [...]
>
> Applied to kvm-x86 misc, thanks!
>
> [1/2] KVM: x86: Fix a comment inside kvm_vcpu_update_apicv()
> https://github.com/kvm-x86/linux/commit/e9e1cb4d5502
> [2/2] KVM: x86: Fix a comment inside __kvm_set_or_clear_apicv_inhibit()
> https://github.com/kvm-x86/linux/commit/8eada24a8e83
FYI, I rebased misc to v6.12-rc5, as patches in another series had already been
taken through the tip tree. New hashes:
[1/2] KVM: x86: Fix a comment inside kvm_vcpu_update_apicv()
https://github.com/kvm-x86/linux/commit/ef86fe036d0a
[2/2] KVM: x86: Fix a comment inside __kvm_set_or_clear_apicv_inhibit()
https://github.com/kvm-x86/linux/commit/6e44d2427b70
prev parent reply other threads:[~2024-11-01 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 10:45 [PATCH 0/2] Fixup two comments Kai Huang
2024-10-08 10:45 ` [PATCH 1/2] KVM: x86: Fix a comment inside kvm_vcpu_update_apicv() Kai Huang
2024-10-08 10:45 ` [PATCH 2/2] KVM: x86: Fix a comment inside __kvm_set_or_clear_apicv_inhibit() Kai Huang
2024-10-31 19:51 ` [PATCH 0/2] Fixup two comments Sean Christopherson
2024-11-01 19:25 ` Sean Christopherson [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=ZyUrRP7sa3IqsVwP@google.com \
--to=seanjc@google.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.