From: Lei Li <lilei@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, mjt@tls.msk.ru,
Lei Li <lilei@linux.vnet.ibm.com>,
quintela@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Trivial fixes for migration
Date: Mon, 27 May 2013 18:33:00 +0800 [thread overview]
Message-ID: <1369650782-14608-1-git-send-email-lilei@linux.vnet.ibm.com> (raw)
This small series improves the document migration.txt
and remove a duplicated setting of bandwidth_limit.
Lei Li (2):
docs: Fix typo and update file in migration
migration: Remove duplicate bandwidth_limit set
docs/migration.txt | 17 +++++++++--------
migration.c | 1 -
2 files changed, 9 insertions(+), 9 deletions(-)
next reply other threads:[~2013-05-27 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 10:33 Lei Li [this message]
2013-05-27 10:33 ` [Qemu-devel] [PATCH 1/2] docs: Fix typo and update file in migration Lei Li
2013-05-27 10:33 ` [Qemu-devel] [PATCH 2/2] migration: Remove duplicate bandwidth_limit set Lei Li
2013-05-27 11:39 ` [Qemu-devel] [PATCH 0/2] Trivial fixes for migration Michael Tokarev
2013-05-27 19:49 ` Michael Tokarev
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=1369650782-14608-1-git-send-email-lilei@linux.vnet.ibm.com \
--to=lilei@linux.vnet.ibm.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).