From: Markus Armbruster <armbru@redhat.com>
To: Ani Sinha <anisinha@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Zhao Liu <zhao1.liu@intel.com>,
cfontana@suse.de, qemu-trivial@nongnu.org, kvm@vger.kernel.org,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH v4 2/2] kvm: refactor core virtual machine creation into its own function
Date: Wed, 28 Aug 2024 07:33:55 +0200 [thread overview]
Message-ID: <87a5gxgqik.fsf@pond.sub.org> (raw)
In-Reply-To: <CAK3XEhPPWvRuzc=DZiP0ni-c9-KsT6=R+9_XAM5224KsiARh=g@mail.gmail.com> (Ani Sinha's message of "Tue, 27 Aug 2024 21:05:41 +0530")
Ani Sinha <anisinha@redhat.com> writes:
> On Tue, 27 Aug, 2024, 8:59 pm Peter Maydell, <peter.maydell@linaro.org>
> wrote:
>
>> On Tue, 27 Aug 2024 at 16:11, Ani Sinha <anisinha@redhat.com> wrote:
>> >
>> > Refactoring the core logic around KVM_CREATE_VM into its own separate
>> function
>> > so that it can be called from other functions in subsequent patches.
>> There is
>> > no functional change in this patch.
>>
>> What subsequent patches? This is patch 2 of 2...
>
> I intend to post them later as a part of a larger patch series when my
> changes have stabilized.
Call them "future patches" then :)
prev parent reply other threads:[~2024-08-28 5:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 15:10 [PATCH 0/2] Some refactoring Ani Sinha
2024-08-27 15:10 ` [PATCH v4 1/2] kvm: replace fprintf with error_report/printf() in kvm_init() Ani Sinha
2024-08-28 6:15 ` Markus Armbruster
2024-08-27 15:10 ` [PATCH v4 2/2] kvm: refactor core virtual machine creation into its own function Ani Sinha
2024-08-27 15:28 ` Peter Maydell
2024-08-27 15:35 ` Ani Sinha
2024-08-28 5:33 ` Markus Armbruster [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=87a5gxgqik.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=anisinha@redhat.com \
--cc=cfontana@suse.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhao1.liu@intel.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.