qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: amit.shah@redhat.com, peter.maydell@linaro.org,
	qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/5] Start migrating migration code into a migration directory
Date: Thu, 18 Dec 2014 12:10:19 +1100	[thread overview]
Message-ID: <20141218011019.GA12159@voom.redhat.com> (raw)
In-Reply-To: <1418382822-25151-2-git-send-email-dgilbert@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

On Fri, Dec 12, 2014 at 11:13:38AM +0000, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> The migration code now occupies a fair chunk of the top level .c
> files, it seems time to give it it's own directory.
> 
> I've not touched:
>    arch_init.c - that's mostly RAM migration but has a few random other
>                  bits
>    savevm.c    - because it's built target specific
> 
> This is purely a code move; no code has changed.
>    - it fails checkpatch because of old violations, it feels safer
>      to keep this as purely a move and fix those at some mythical future
>      date.
> 
> The xbzrle and vmstate tests are now only run for softmmu builds
> since they require files in the migrate/ directory which is only built
> for softmmu.
> 
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-12-18  1:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 11:13 [Qemu-devel] [PATCH v3 0/5] More migration file cleanup Dr. David Alan Gilbert (git)
2014-12-12 11:13 ` [Qemu-devel] [PATCH v3 1/5] Start migrating migration code into a migration directory Dr. David Alan Gilbert (git)
2014-12-18  1:10   ` David Gibson [this message]
2014-12-12 11:13 ` [Qemu-devel] [PATCH v3 2/5] Remove migration- pre/post fixes off files in migration/ dir Dr. David Alan Gilbert (git)
2014-12-18  1:10   ` David Gibson
2014-12-12 11:13 ` [Qemu-devel] [PATCH v3 3/5] Split struct QEMUFile out Dr. David Alan Gilbert (git)
2014-12-18  1:11   ` David Gibson
2014-12-12 11:13 ` [Qemu-devel] [PATCH v3 4/5] Split the QEMU buffered file code out Dr. David Alan Gilbert (git)
2014-12-18  1:13   ` David Gibson
2014-12-18  9:24     ` Dr. David Alan Gilbert
2014-12-19 13:27       ` Eduardo Habkost
2014-12-24 14:11         ` David Gibson
2015-01-15 16:02       ` Stefan Berger
2014-12-12 11:13 ` [Qemu-devel] [PATCH v3 5/5] MAINTAINERS: Update for migrated migration code Dr. David Alan Gilbert (git)
2014-12-18  1:13   ` David Gibson

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=20141218011019.GA12159@voom.redhat.com \
    --to=david@gibson.dropbear.id.au \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).