From: Wei Yang <richardw.yang@linux.intel.com>
To: qemu-devel@nongnu.org
Cc: Wei Yang <richardw.yang@linux.intel.com>,
dgilbert@redhat.com, quintela@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] migration: cleanup ram_load
Date: Thu, 25 Jul 2019 08:20:21 +0800 [thread overview]
Message-ID: <20190725002023.2335-1-richardw.yang@linux.intel.com> (raw)
Two cleanup for ram_load:
* return -EINVAL for version_id mismatch
* extract ram_load_precopy for better readability
v2: fix a comment
Wei Yang (2):
migration: return -EINVAL directly when version_id mismatch
migration: extract ram_load_precopy
migration/ram.c | 73 +++++++++++++++++++++++++++++++------------------
1 file changed, 46 insertions(+), 27 deletions(-)
--
2.17.1
next reply other threads:[~2019-07-25 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 0:20 Wei Yang [this message]
2019-07-25 0:20 ` [Qemu-devel] [PATCH v2 1/2] migration: return -EINVAL directly when version_id mismatch Wei Yang
2019-07-25 0:20 ` [Qemu-devel] [PATCH v2 2/2] migration: extract ram_load_precopy Wei Yang
2019-08-07 17:54 ` [Qemu-devel] [PATCH v2 0/2] migration: cleanup ram_load 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=20190725002023.2335-1-richardw.yang@linux.intel.com \
--to=richardw.yang@linux.intel.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).