From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
peterx@redhat.com,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/2] migration: fixes for 2.10
Date: Wed, 2 Aug 2017 17:41:18 +0800 [thread overview]
Message-ID: <1501666880-10159-1-git-send-email-peterx@redhat.com> (raw)
v2:
- patch 2: move trace_*() after error_setg_errno(). [Dan]
Two patches isolated from the postcopy recovery series, which may be
good for 2.10.
Peter Xu (2):
migration: fix comment disorder in RAMState
io: fix qio_channel_socket_accept err handling
io/channel-socket.c | 3 ++-
migration/ram.c | 4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2017-08-02 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 9:41 Peter Xu [this message]
2017-08-02 9:41 ` [Qemu-devel] [PATCH v2 1/2] migration: fix comment disorder in RAMState Peter Xu
2017-08-02 9:41 ` [Qemu-devel] [PATCH v2 2/2] io: fix qio_channel_socket_accept err handling Peter Xu
2017-08-02 9:42 ` Daniel P. Berrange
2017-08-02 10:29 ` [Qemu-devel] [PATCH v2 0/2] migration: fixes for 2.10 Dr. David Alan Gilbert
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=1501666880-10159-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@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).