From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: quintela@trasno.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: [PATCH v2 0/3] Migration Pull request
Date: Mon, 13 Jul 2020 17:58:24 +0200 [thread overview]
Message-ID: <20200713155827.10670-1-quintela@redhat.com> (raw)
It includes several fixes:
- fix qemu_fclose(denis)
- remove superfluous breaks (liao)
- fix memory leak (zheng)
Please apply
Denis V. Lunev (1):
migration/savevm: respect qemu_fclose() error code in save_snapshot()
Liao Pingfang (1):
migration/migration.c: Remove superfluous breaks
Zheng Chuan (1):
migration: fix memory leak in qmp_migrate_set_parameters
migration/migration.c | 6 ++----
migration/savevm.c | 8 ++++++--
2 files changed, 8 insertions(+), 6 deletions(-)
--
2.25.4
next reply other threads:[~2020-07-13 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 15:58 Juan Quintela [this message]
2020-07-13 15:58 ` [PATCH v2 2/3] migration/savevm: respect qemu_fclose() error code in save_snapshot() Juan Quintela
2020-07-13 15:58 ` [PATCH v2 3/3] migration/migration.c: Remove superfluous breaks 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=20200713155827.10670-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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).