From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, jdenemar@redhat.com
Subject: [Qemu-devel] [PATCH 1/3] migration: Remove duplicated assignement of SETUP status
Date: Wed, 20 May 2015 17:35:22 +0200 [thread overview]
Message-ID: <1432136124-24572-2-git-send-email-quintela@redhat.com> (raw)
In-Reply-To: <1432136124-24572-1-git-send-email-quintela@redhat.com>
We assign the MIGRATION_STATUS_SETUP status in two places. Just in
sucession. Just remove the second one.
Signed-off-by: Juan Quintela <quintela@redhat.com>
---
migration/migration.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/migration/migration.c b/migration/migration.c
index 1035689..2925587 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -849,9 +849,6 @@ static void *migration_thread(void *opaque)
void migrate_fd_connect(MigrationState *s)
{
- s->state = MIGRATION_STATUS_SETUP;
- trace_migrate_set_state(MIGRATION_STATUS_SETUP);
-
/* This is a best 1st approximation. ns to ms */
s->expected_downtime = max_downtime/1000000;
s->cleanup_bh = qemu_bh_new(migrate_fd_cleanup, s);
--
2.4.1
next prev parent reply other threads:[~2015-05-20 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 15:35 [Qemu-devel] [PATCH v4 0/3] Migration Events Juan Quintela
2015-05-20 15:35 ` Juan Quintela [this message]
2015-05-20 15:58 ` [Qemu-devel] [PATCH 1/3] migration: Remove duplicated assignement of SETUP status Eric Blake
2015-05-20 16:03 ` John Snow
2015-06-03 9:14 ` Juan Quintela
2015-05-20 15:35 ` [Qemu-devel] [PATCH 2/3] migration: create migration event Juan Quintela
2015-05-20 16:02 ` Eric Blake
2015-05-21 9:49 ` Juan Quintela
2015-06-17 0:20 ` Juan Quintela
2015-05-29 11:45 ` Jiri Denemark
2015-06-17 0:12 ` Juan Quintela
2015-05-20 15:35 ` [Qemu-devel] [PATCH 3/3] migration: Add migration events on target side Juan Quintela
2015-05-20 16:10 ` Eric Blake
2015-05-21 9:57 ` Juan Quintela
2015-06-02 12:44 ` [Qemu-devel] [PATCH v4 0/3] Migration Events Jiri Denemark
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=1432136124-24572-2-git-send-email-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=amit.shah@redhat.com \
--cc=jdenemar@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).