From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: roy.hopkins@suse.com, seanjc@google.com, michael.roth@amd.com,
ashish.kalra@amd.com, jroedel@suse.de, thomas.lendacky@amd.com,
nsaenz@amazon.com, anelkz@amazon.de, oliver.upton@linux.dev,
isaku.yamahata@intel.com, maz@kernel.org, steven.price@arm.com,
kai.huang@intel.com, rick.p.edgecombe@intel.com,
James.Bottomley@HansenPartnership.com
Subject: Re: [RFC PATCH 0/5] Documentation: kvm: cleanup and introduce "VM planes"
Date: Fri, 8 Nov 2024 10:07:36 +0100 [thread overview]
Message-ID: <fda9058a-d3f2-45e8-a0d5-ee51284b9582@redhat.com> (raw)
In-Reply-To: <20241023124507.280382-1-pbonzini@redhat.com>
On 10/23/24 14:45, Paolo Bonzini wrote:
> In order to add the relevant text, there are a few cleanups that can be applied
> separately.
Applied patches 1-4.
Paolo
prev parent reply other threads:[~2024-11-08 9:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 12:45 [RFC PATCH 0/5] Documentation: kvm: cleanup and introduce "VM planes" Paolo Bonzini
2024-10-23 12:45 ` [RFC PATCH 1/5] KVM: powerpc: remove remaining traces of KVM_CAP_PPC_RMA Paolo Bonzini
2024-10-23 12:45 ` [RFC PATCH 2/5] Documentation: kvm: fix a few mistakes Paolo Bonzini
2024-10-23 12:45 ` [RFC PATCH 3/5] Documentation: kvm: replace section numbers with links Paolo Bonzini
2024-10-23 12:45 ` [RFC PATCH 4/5] Documentation: kvm: reorganize introduction Paolo Bonzini
2024-10-23 12:45 ` [PATCH 5/5] Documentation: kvm: introduce "VM plane" concept Paolo Bonzini
2025-01-17 21:48 ` Sean Christopherson
2025-01-21 10:50 ` Nicolas Saenz Julienne
2025-01-21 17:20 ` Sean Christopherson
2025-01-21 18:34 ` Nicolas Saenz Julienne
2024-11-08 9:07 ` 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=fda9058a-d3f2-45e8-a0d5-ee51284b9582@redhat.com \
--to=pbonzini@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=anelkz@amazon.de \
--cc=ashish.kalra@amd.com \
--cc=isaku.yamahata@intel.com \
--cc=jroedel@suse.de \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=michael.roth@amd.com \
--cc=nsaenz@amazon.com \
--cc=oliver.upton@linux.dev \
--cc=rick.p.edgecombe@intel.com \
--cc=roy.hopkins@suse.com \
--cc=seanjc@google.com \
--cc=steven.price@arm.com \
--cc=thomas.lendacky@amd.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