From: Peter Xu <peterx@redhat.com>
To: Het Gala <het.gala@nutanix.com>
Cc: qemu-devel@nongnu.org, prerna.saxena@nutanix.com,
quintela@redhat.com, dgilbert@redhat.com, pbonzini@redhat.com,
berrange@redhat.com, armbru@redhat.com, eblake@redhat.com,
manish.mishra@nutanix.com, aravind.retnakaran@nutanix.com
Subject: Re: [PATCH v10 00/10] migration: Modify 'migrate' and 'migrate-incoming' QAPI commands for migration
Date: Mon, 21 Aug 2023 12:36:09 -0400 [thread overview]
Message-ID: <ZOOSecV/AcAwbgzl@x1n> (raw)
In-Reply-To: <3fb6b8c1-7790-3ad6-62b1-81642e878f7d@nutanix.com>
Het,
On Mon, Aug 21, 2023 at 11:43:02AM +0530, Het Gala wrote:
> Hi qemu-devel community,
>
> A gentle reminder and request for all migration maintainers - Peter, Juan,
> Dr. Gilbert and others too for review of the patchset series. Received
> reviewed-by from Daniel on migration implementation patches but need final
> approval from migration maintainers before getting it merged. Also got
> acked-by tag from Markus on the QAPI patches. This is Part1 of the 4
> patchset series. Ultimate goal of the whole 4 series is to 'introduce
> multiple interface support on top of existing multifd capability'. Hope to
> get approval or comments from migration maintainers on the patches soon.
This all looks right to me from high level. I'd just trust Daniel's in
depth review already, considering that Juan will probably give a final
round of look soon, anyway.
Juan was just busy in the past few weeks; I suppose he'll catch up very
soon.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2023-08-21 16:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 14:18 [PATCH v10 00/10] migration: Modify 'migrate' and 'migrate-incoming' QAPI commands for migration Het Gala
2023-07-26 14:18 ` [PATCH v10 01/10] migration: New QAPI type 'MigrateAddress' Het Gala
2023-07-26 14:18 ` [PATCH v10 02/10] migration: convert migration 'uri' into 'MigrateAddress' Het Gala
2023-07-26 14:18 ` [PATCH v10 03/10] migration: convert socket backend to accept MigrateAddress Het Gala
2023-07-26 14:18 ` [PATCH v10 04/10] migration: convert rdma " Het Gala
2023-07-26 14:18 ` [PATCH v10 05/10] migration: convert exec " Het Gala
2023-07-26 14:18 ` [PATCH v10 06/10] migration: New migrate and migrate-incoming argument 'channels' Het Gala
2023-07-26 14:53 ` Daniel P. Berrangé
2023-07-26 14:18 ` [PATCH v10 07/10] migration: modify migration_channels_and_uri_compatible() for new QAPI syntax Het Gala
2023-07-26 14:18 ` [PATCH v10 08/10] migration: Implement MigrateChannelList to qmp migration flow Het Gala
2023-07-26 14:54 ` Daniel P. Berrangé
2023-07-26 14:18 ` [PATCH v10 09/10] migration: Implement MigrateChannelList to hmp " Het Gala
2023-07-26 14:55 ` Daniel P. Berrangé
2023-07-26 16:38 ` Het Gala
2023-07-26 16:41 ` Daniel P. Berrangé
2023-07-26 17:07 ` Het Gala
2023-07-26 14:18 ` [PATCH v10 10/10] migration: modify test_multifd_tcp_none() to use new QAPI syntax Het Gala
2023-07-27 11:29 ` [PATCH v10 00/10] migration: Modify 'migrate' and 'migrate-incoming' QAPI commands for migration Het Gala
2023-08-03 5:43 ` Het Gala
2023-08-21 6:13 ` Het Gala
2023-08-21 16:36 ` Peter Xu [this message]
2023-09-05 13:22 ` Fabiano Rosas
2023-10-04 5:01 ` Het Gala
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=ZOOSecV/AcAwbgzl@x1n \
--to=peterx@redhat.com \
--cc=aravind.retnakaran@nutanix.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=het.gala@nutanix.com \
--cc=manish.mishra@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=prerna.saxena@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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;
as well as URLs for NNTP newsgroup(s).