From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, lvivier@redhat.com, peterx@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] Migration patches on queue for 2.12
Date: Fri, 1 Dec 2017 13:57:25 +0100 [thread overview]
Message-ID: <20171201125728.1310-1-quintela@redhat.com> (raw)
Hi
Sending them because my next series are on top of this ones.
Later, Juan.
Juan Quintela (3):
migration: Use proper types in json
migration: print features as on off
migration: free addr in the same function that we created it
hmp.c | 22 +++++++++---------
migration/migration.c | 62 ++++++++++++++++++++++++---------------------------
migration/socket.c | 4 ++--
qapi/migration.json | 20 ++++++++---------
4 files changed, 52 insertions(+), 56 deletions(-)
--
2.14.3
next reply other threads:[~2017-12-01 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 12:57 Juan Quintela [this message]
2017-12-01 12:57 ` [Qemu-devel] [PATCH 1/3] migration: Use proper types in json Juan Quintela
2017-12-01 12:57 ` [Qemu-devel] [PATCH 2/3] migration: print features as on off Juan Quintela
2017-12-01 12:57 ` [Qemu-devel] [PATCH 3/3] migration: free addr in the same function that we created it 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=20171201125728.1310-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@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).