From: Amit Shah <amit.shah@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] Use getaddrinfo for migration
Date: Wed, 23 Mar 2011 16:56:28 +0530 [thread overview]
Message-ID: <20110323112628.GD23466@amit-x200.redhat.com> (raw)
In-Reply-To: <abecb2533cad1d5e186bc29c7799c96d0c449433.1300454243.git.quintela@redhat.com>
On (Fri) 18 Mar 2011 [14:22:49], Juan Quintela wrote:
> This allows us to use ipv4/ipv6 for migration addresses.
> Once there, it also uses /etc/services names (it came free).
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> ---
> migration-tcp.c | 51 +++++++--------------------
> net.c | 106 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> qemu_socket.h | 3 ++
> 3 files changed, 122 insertions(+), 38 deletions(-)
>
> diff --git a/migration-tcp.c b/migration-tcp.c
> index 2340b55..2fa496a 100644
> --- a/migration-tcp.c
> +++ b/migration-tcp.c
> @@ -48,8 +48,6 @@ static int tcp_close(FdMigrationState *s)
> }
> return 0;
> }
> -
> -
> static void tcp_wait_for_connect(void *opaque)
Another nitpick: one newline should be kept.
Amit
next prev parent reply other threads:[~2011-03-23 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 13:22 [Qemu-devel] [PATCH v2 0/3] Allow ipv6 for migration Juan Quintela
2011-03-18 13:22 ` [Qemu-devel] [PATCH 1/3] create socket_set_reuseaddr() Juan Quintela
2011-03-23 11:25 ` Amit Shah
2011-03-18 13:22 ` [Qemu-devel] [PATCH 2/3] Use getaddrinfo for migration Juan Quintela
2011-03-23 11:26 ` Amit Shah [this message]
2011-03-18 13:22 ` [Qemu-devel] [PATCH 3/3] net/socket: allow ipv6 for net_socket_listen_init and net_socket_connect_init Juan Quintela
2011-03-23 11:25 ` [Qemu-devel] [PATCH v2 0/3] Allow ipv6 for migration Amit Shah
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=20110323112628.GD23466@amit-x200.redhat.com \
--to=amit.shah@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).