From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/8] KVM: cleanup linux/kvm.h
Date: Thu, 8 Feb 2024 09:10:46 -0800 [thread overview]
Message-ID: <ZcULFqXM_sA3dSY7@google.com> (raw)
In-Reply-To: <CABgObfa1SmH0HDq5B5OQxpueej=bdivMTkVrO=cXNfOi09HhUw@mail.gmail.com>
On Thu, Feb 08, 2024, Paolo Bonzini wrote:
> On Wed, Feb 7, 2024 at 3:43 PM Sean Christopherson <seanjc@google.com> wrote:
> >
> > On Wed, Jan 31, 2024, Paolo Bonzini wrote:
> > > More cleanups of KVM's main header:
> > >
> > > * remove thoroughly obsolete APIs
> > >
> > > * move architecture-dependent stuff to uapi/asm/kvm.h
> > >
> > > * small cleanups to __KVM_HAVE_* symbols
> >
> > Do you have any thoughts on how/when you're going to apply this? The kvm.h code
> > movement is likely going to generate conflicts for any new uAPI, e.g. I know Paul's
> > Xen series at least conflicts.
>
> It also conflicts (and was partly motivated by) the SEV API cleanups
> that I am going to post soon.
>
> > A topic branch is probably overkill. Maybe getting this into kvm/next sooner
> > than later so that kvm/next can be used as a base will suffice?
>
> I can do both, a topic branch is free. But if you think this is in the
> "if it compiles, apply it", then I can take that as Acked-by and apply
> it today or tomorrow.
Looks like you already created and merged a topic branch, but for giggles:
Acked-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2024-02-08 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 23:30 [PATCH 0/8] KVM: cleanup linux/kvm.h Paolo Bonzini
2024-01-31 23:30 ` [PATCH 1/8] KVM: remove more traces of device assignment UAPI Paolo Bonzini
2024-01-31 23:30 ` [PATCH 2/8] KVM: x86: move x86-specific structs to uapi/asm/kvm.h Paolo Bonzini
2024-01-31 23:30 ` [PATCH 3/8] KVM: powerpc: move powerpc-specific " Paolo Bonzini
2024-01-31 23:30 ` [PATCH 4/8] KVM: s390: move s390-specific " Paolo Bonzini
2024-01-31 23:30 ` [PATCH 5/8] KVM: arm64: move ARM-specific defines " Paolo Bonzini
2024-01-31 23:30 ` [PATCH 6/8] kvm: replace __KVM_HAVE_READONLY_MEM with Kconfig symbol Paolo Bonzini
2024-01-31 23:30 ` [PATCH 7/8] KVM: define __KVM_HAVE_GUEST_DEBUG unconditionally Paolo Bonzini
2024-01-31 23:30 ` [PATCH 8/8] KVM: remove unnecessary #ifdef Paolo Bonzini
2024-02-07 14:42 ` [PATCH 0/8] KVM: cleanup linux/kvm.h Sean Christopherson
2024-02-08 13:39 ` Paolo Bonzini
2024-02-08 17:10 ` Sean Christopherson [this message]
2024-02-08 17:32 ` Paolo Bonzini
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=ZcULFqXM_sA3dSY7@google.com \
--to=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox