From: Peter Xu <peterx@redhat.com>
To: "manish.mishra" <manish.mishra@nutanix.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
"Leonardo Bras Soares Passos" <lsoaresp@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH 1/5] io: Add support for MSG_PEEK for socket channel
Date: Fri, 16 Dec 2022 09:30:19 -0500 [thread overview]
Message-ID: <Y5yA+64lVSmG5nQk@x1n> (raw)
In-Reply-To: <400814c5-f179-2566-e513-543ae4ae34e4@nutanix.com>
On Fri, Dec 16, 2022 at 04:10:22PM +0530, manish.mishra wrote:
> Yes sorry, noticed it now, should i send another patch to update it. Also
> in our internal testing we noticed multifd_init was skipped for 1 case,
> so if this patch series is not yet submitted should i send another
> version of it early morning monday?
I think yes.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2022-12-16 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 21:38 [PATCH 0/5] migration: Fix disorder of channel creations Peter Xu
2022-12-13 21:38 ` [PATCH 1/5] io: Add support for MSG_PEEK for socket channel Peter Xu
2022-12-14 9:14 ` Daniel P. Berrangé
2022-12-14 21:30 ` Peter Xu
2022-12-15 9:40 ` Daniel P. Berrangé
2022-12-15 17:35 ` Peter Xu
2022-12-16 10:40 ` manish.mishra
2022-12-16 14:30 ` Peter Xu [this message]
2022-12-13 21:38 ` [PATCH 2/5] migration: check magic value for deciding the mapping of channels Peter Xu
2022-12-14 9:15 ` Daniel P. Berrangé
2022-12-13 21:38 ` [PATCH 3/5] migration: Rework multi-channel checks on URI Peter Xu
2022-12-13 21:38 ` [PATCH 4/5] migration: Add a semaphore to count PONGs Peter Xu
2022-12-13 21:38 ` [PATCH 5/5] migration: Postpone postcopy preempt channel to be after main Peter Xu
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=Y5yA+64lVSmG5nQk@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=manish.mishra@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).