From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.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 18:32:09 +0100 [thread overview]
Message-ID: <CABgObfYMg_7b4U=RXSz0c8ouo5UKqpP2Ra48jkq9Gur7fFKs4g@mail.gmail.com> (raw)
In-Reply-To: <ZcULFqXM_sA3dSY7@google.com>
On Thu, Feb 8, 2024 at 6:10 PM Sean Christopherson <seanjc@google.com> wrote:
> > 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:
Only to kvm/queue to show myself how it would look like...
> Acked-by: Sean Christopherson <seanjc@google.com>
Thanks!
Paolo
prev parent reply other threads:[~2024-02-08 17:32 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
2024-02-08 17:32 ` Paolo Bonzini [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='CABgObfYMg_7b4U=RXSz0c8ouo5UKqpP2Ra48jkq9Gur7fFKs4g@mail.gmail.com' \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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.