From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>, kvm <kvm@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] KVM: VMX: Stub out enable_evmcs static key
Date: Tue, 14 Mar 2023 17:05:24 -0700 [thread overview]
Message-ID: <ZBEE1GafxqQkjYuk@google.com> (raw)
In-Reply-To: <CABgObfZoQAis56NaVO0Pi6U_BsY3_Ue41mOJGQtXTWex2D2Wpg@mail.gmail.com>
On Tue, Mar 14, 2023, Paolo Bonzini wrote:
> Il mar 14 mar 2023, 15:29 Sean Christopherson <seanjc@google.com> ha scritto:
> >
> > On Tue, Mar 14, 2023, Paolo Bonzini wrote:
> > > Queued, thanks.
> >
> > Paolo,
> >
> > Are you grabbing this for 6.3 or 6.4? If it's for 6.4, what is your plan for 6.4?
> > I assumed we were taking the same approach as we did for 6.3, where you handle the
> > current cycle (stabilizing 6.3) and I focus on the next cycle (building 6.4).
>
>
> This one is for 6.4. What we did for 6.3 included me merging a handful
> of series that were not included in the previous merge window; so
> that's what I did today. If that's okay for you, once the -rc3 pull
> request is sent (probably tomorrow) I will push to kvm/next and that
> will be it.
Works for me, thanks!
prev parent reply other threads:[~2023-03-15 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 0:35 [PATCH v2 0/3] KVM: VMX: Stub out enable_evmcs static key Sean Christopherson
2023-02-11 0:35 ` [PATCH v2 1/3] KVM: nVMX: Move EVMCS1_SUPPORT_* macros to hyperv.c Sean Christopherson
2023-02-11 0:35 ` [PATCH v2 2/3] KVM: VMX: Stub out enable_evmcs static key for CONFIG_HYPERV=n Sean Christopherson
2023-02-11 0:35 ` [PATCH v2 3/3] KVM: VMX: Rename "KVM is using eVMCS" static key to match its wrapper Sean Christopherson
2023-02-13 11:54 ` Vitaly Kuznetsov
2023-03-14 13:43 ` [PATCH v2 0/3] KVM: VMX: Stub out enable_evmcs static key Paolo Bonzini
2023-03-14 14:28 ` Sean Christopherson
2023-03-14 22:43 ` Paolo Bonzini
2023-03-15 0:05 ` 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=ZBEE1GafxqQkjYuk@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@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.