From: Juan Quintela <quintela@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Leonardo Bras <leobras@redhat.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH 4/5] migration/rdma: It makes no sense to recive that flag without RDMA
Date: Fri, 05 May 2023 00:53:39 +0200 [thread overview]
Message-ID: <87y1m3ogi4.fsf@secure.mitica> (raw)
In-Reply-To: <ZFPl0Slq5vX4VuBl@redhat.com> ("Daniel P. Berrangé"'s message of "Thu, 4 May 2023 18:05:21 +0100")
Daniel P. Berrangé <berrange@redhat.com> wrote:
> In $SUBJECT s/recive/receive/
>
> On Thu, May 04, 2023 at 01:44:42PM +0200, Juan Quintela wrote:
>> This could only happen if the source send
>
> s/send/sent/
Fixed.
>> RAM_SAVE_FLAG_HOOK (i.e. rdma) and destination don't have CONFIG_RDMA.
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> ---
>> migration/qemu-file.c | 8 --------
>> 1 file changed, 8 deletions(-)
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Thanks.
next prev parent reply other threads:[~2023-05-04 22:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 11:44 [PATCH 0/5] Migration RDMA cleanup Juan Quintela
2023-05-04 11:44 ` [PATCH 1/5] migration: Make RAM_SAVE_FLAG_HOOK a normal case entry Juan Quintela
2023-05-04 17:03 ` Daniel P. Berrangé
2023-05-26 21:09 ` Peter Xu
2023-05-04 11:44 ` [PATCH 2/5] migration/rdma: simplify ram_control_load_hook() Juan Quintela
2023-05-04 17:03 ` Daniel P. Berrangé
2023-05-26 21:10 ` Peter Xu
2023-05-04 11:44 ` [PATCH 3/5] migration/rdma: We can calculate the rioc from the QEMUFile Juan Quintela
2023-05-04 17:04 ` Daniel P. Berrangé
2023-05-26 21:10 ` Peter Xu
2023-05-04 11:44 ` [PATCH 4/5] migration/rdma: It makes no sense to recive that flag without RDMA Juan Quintela
2023-05-04 17:05 ` Daniel P. Berrangé
2023-05-04 22:53 ` Juan Quintela [this message]
2023-05-26 21:15 ` Peter Xu
2023-05-04 11:44 ` [PATCH 5/5] migration/rdma: Check for postcopy sooner Juan Quintela
2023-05-04 17:05 ` Daniel P. Berrangé
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=87y1m3ogi4.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).