From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
pbonzini@redhat.com, maz@kernel.org,
Wang Yong <yongw.kernel@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: update code comment in struct kvm_vcpu
Date: Wed, 8 Feb 2023 02:02:19 +0000 [thread overview]
Message-ID: <167582153155.456727.4672588708621236361.b4-ty@google.com> (raw)
In-Reply-To: <20230202081342.856687-1-yongw.kernel@gmail.com>
On Thu, 02 Feb 2023 08:13:42 +0000, Wang Yong wrote:
> Commit c5b077549136 ("KVM: Convert the kvm->vcpus array to a xarray")
> changed kvm->vcpus array to a xarray, so update the code comment of
> kvm_vcpu->vcpu_idx accordingly.
>
>
Applied to kvm-x86 generic, thanks!
[1/1] KVM: update code comment in struct kvm_vcpu
https://github.com/kvm-x86/linux/commit/5bad5d55d884
--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes
prev parent reply other threads:[~2023-02-08 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 8:13 [PATCH] KVM: update code comment in struct kvm_vcpu Wang Yong
2023-02-08 2:02 ` 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=167582153155.456727.4672588708621236361.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=yongw.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).