From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: "quintela@redhat.com" <quintela@redhat.com>,
"dgilbert@redhat.com" <dgilbert@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] migration/rdma: Remove deprecated variable rdma_return_path
Date: Thu, 16 Mar 2023 08:51:47 +0000 [thread overview]
Message-ID: <baf1970f-d68a-dba4-cb6d-312431f2ff0e@fujitsu.com> (raw)
In-Reply-To: <20230315012247.9007-1-lizhijian@fujitsu.com>
Not clear why it doesn't appear in the archive(https://lists.gnu.org/archive/html/qemu-devel/2023-03/threads.html)
nop...
On 15/03/2023 09:22, Li Zhijian wrote:
> It's no longer needed since commit
> 44bcfd45e98 ("migration/rdma: destination: create the return patch after the first accept")
>
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> ---
> migration/rdma.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/migration/rdma.c b/migration/rdma.c
> index f5d3bbe7e9c..2bc2fcf727b 100644
> --- a/migration/rdma.c
> +++ b/migration/rdma.c
> @@ -4214,7 +4214,7 @@ static void rdma_accept_incoming_migration(void *opaque)
> void rdma_start_incoming_migration(const char *host_port, Error **errp)
> {
> int ret;
> - RDMAContext *rdma, *rdma_return_path = NULL;
> + RDMAContext *rdma;
> Error *local_err = NULL;
>
> trace_rdma_start_incoming_migration();
> @@ -4260,7 +4260,6 @@ err:
> g_free(rdma->host_port);
> }
> g_free(rdma);
> - g_free(rdma_return_path);
> }
>
> void rdma_start_outgoing_migration(void *opaque,
next parent reply other threads:[~2023-03-16 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230315012247.9007-1-lizhijian@fujitsu.com>
2023-03-16 8:51 ` lizhijian [this message]
2023-03-16 9:59 ` [PATCH] migration/rdma: Remove deprecated variable rdma_return_path Juan Quintela
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=baf1970f-d68a-dba4-cb6d-312431f2ff0e@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=dgilbert@redhat.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).