qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] migration: Remove unneeded includes
Date: Wed, 14 Jun 2017 09:16:59 +0200	[thread overview]
Message-ID: <87wp8ff384.fsf@secure.mitica> (raw)
In-Reply-To: <20170614063914.GI11751@pxdev.xzpeter.org> (Peter Xu's message of "Wed, 14 Jun 2017 14:39:14 +0800")

Peter Xu <peterx@redhat.com> wrote:
> On Tue, Jun 13, 2017 at 11:52:51AM +0200, Juan Quintela wrote:
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> ---
>>  include/migration/colo.h  | 3 ---
>>  include/migration/misc.h  | 2 ++
>>  migration/block.c         | 6 ------
>>  migration/colo-failover.c | 2 ++
>>  migration/colo.c          | 2 --
>>  migration/exec.c          | 2 --
>>  migration/fd.c            | 2 --
>>  migration/global_state.c  | 1 -
>>  migration/migration.c     | 6 ------
>>  migration/migration.h     | 2 --
>>  migration/postcopy-ram.c  | 4 +---
>>  migration/qemu-file.c     | 2 --
>>  migration/ram.c           | 4 ----
>>  migration/savevm.c        | 6 ------
>>  14 files changed, 5 insertions(+), 39 deletions(-)
>> 
>> diff --git a/include/migration/colo.h b/include/migration/colo.h
>> index ba0bb6e..be6beba 100644
>> --- a/include/migration/colo.h
>> +++ b/include/migration/colo.h
>> @@ -14,9 +14,6 @@
>>  #define QEMU_COLO_H
>>  
>>  #include "qemu-common.h"
>> -#include "qemu/coroutine_int.h"
>> -#include "qemu/thread.h"
>> -#include "qemu/main-loop.h"
>>  
>>  bool colo_supported(void);
>>  void colo_info_init(void);
>> diff --git a/include/migration/misc.h b/include/migration/misc.h
>> index d5a433a..65c7070 100644
>> --- a/include/migration/misc.h
>> +++ b/include/migration/misc.h
>> @@ -14,6 +14,8 @@
>>  #ifndef MIGRATION_MISC_H
>>  #define MIGRATION_MISC_H
>>  
>> +#include "qemu/notify.h"
>> +
>
> Since we added this new line (I believe it's for Notifier), do we need
> to include "qemu/typedefs.h" as well? Since I see Error and
> MigrationState is used as well.

It compiles, so it should be perfect O:-)

>> diff --git a/migration/postcopy-ram.c b/migration/postcopy-ram.c
>> index c8c4500..922702b 100644
>> --- a/migration/postcopy-ram.c
>> +++ b/migration/postcopy-ram.c
>> @@ -17,14 +17,12 @@
>>   */
>>  
>>  #include "qemu/osdep.h"
>> -
>> -#include "qemu-common.h"
>>  #include "exec/target_page.h"
>>  #include "migration.h"
>>  #include "qemu-file.h"
>> -#include "savevm.h"
>>  #include "postcopy-ram.h"
>>  #include "ram.h"
>> +#include "savevm.h"
>
> Just curious about whether there's any specific reason to move this
> line from above to here?
>
> Besides the nits:
>
> Reviewed-by: Peter Xu <peterx@redhat.com>

Rebases O:-)


Thanks, Juan.

      reply	other threads:[~2017-06-14  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  9:52 [Qemu-devel] [PATCH v2] Misc migration cleanups Juan Quintela
2017-06-13  9:52 ` [Qemu-devel] [PATCH v2] migration: Remove unneeded includes Juan Quintela
2017-06-14  6:39   ` Peter Xu
2017-06-14  7:16     ` Juan Quintela [this message]

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=87wp8ff384.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peterx@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).