qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Liang Li <liang.z.li@intel.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: remove useless code.
Date: Thu, 4 Feb 2016 15:35:52 +0530	[thread overview]
Message-ID: <20160204100552.GD20527@grmbl.mre> (raw)
In-Reply-To: <1453875065-24326-1-git-send-email-liang.z.li@intel.com>

On (Wed) 27 Jan 2016 [14:11:05], Liang Li wrote:
> Since 's->state' will be set in migrate_init(), there is no
> need to set it before calling migrate_init(). The code and
> the related comments can be removed.
> 
> Signed-off-by: Liang Li <liang.z.li@intel.com>
> ---
>  migration/migration.c | 6 ------
>  1 file changed, 6 deletions(-)
> 
> diff --git a/migration/migration.c b/migration/migration.c
> index aaca451..ae38242 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -1006,12 +1006,6 @@ void qmp_migrate(const char *uri, bool has_blk, bool blk,
>          return;
>      }
>  
> -    /* We are starting a new migration, so we want to start in a clean
> -       state.  This change is only needed if previous migration
> -       failed/was cancelled.  We don't use migrate_set_state() because
> -       we are setting the initial state, not changing it. */
> -    s->state = MIGRATION_STATUS_NONE;
> -

Looks fine.  This was added to ensure a proper init value, but commit
389775d added the init in migrate_init, so this is now redundant.

Reviewed-by: Amit Shah <amit.shah@redhat.com>


		Amit

  parent reply	other threads:[~2016-02-04 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  6:11 [Qemu-devel] [PATCH] migration: remove useless code Liang Li
2016-01-27  6:59 ` Fam Zheng
2016-01-27  9:08 ` Dr. David Alan Gilbert
2016-02-04 10:05 ` Amit Shah [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-18  9:19 Liang Li
2016-04-18  9:45 ` 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=20160204100552.GD20527@grmbl.mre \
    --to=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=liang.z.li@intel.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).