From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] Move last migration bits into migration/
Date: Fri, 8 May 2015 14:43:14 +0200 [thread overview]
Message-ID: <1431088998-27721-1-git-send-email-quintela@redhat.com> (raw)
Hi
This do:
- split ram migration bits from arch_init.c into migration/ram.c
- move savevm.c into migration/
- add myself to the copyright list of that files
if you feel your name should be there, jsut sent one patch
- to spot changes easily, I reduce the include mess for arch_init.c
and migratio/ram.c in a separate patch. I have been aggresive here,
but it complies on x86_64 and x86 linux, cross compiles for w32 and
w64, so, we should be quite good.
Please, review.
Thanks, Juan.
Juan Quintela (4):
migration: move ram stuff to migration/ram
migration: move savevm.c inside migration/
migration: Add myself to the copyright list of both files
movement: reduce include files
MAINTAINERS | 2 -
Makefile.target | 3 +-
arch_init.c | 1795 ++--------------------------------------
include/migration/migration.h | 2 +
include/sysemu/arch_init.h | 1 -
migration/ram.c | 1671 +++++++++++++++++++++++++++++++++++++
savevm.c => migration/savevm.c | 4 +
trace-events | 4 +-
8 files changed, 1752 insertions(+), 1730 deletions(-)
create mode 100644 migration/ram.c
rename savevm.c => migration/savevm.c (99%)
--
2.4.0
next reply other threads:[~2015-05-08 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 12:43 Juan Quintela [this message]
2015-05-08 12:43 ` [Qemu-devel] [PATCH 1/4] migration: move ram stuff to migration/ram Juan Quintela
2015-05-08 14:11 ` Eric Blake
2015-05-08 12:43 ` [Qemu-devel] [PATCH 2/4] migration: move savevm.c inside migration/ Juan Quintela
2015-05-08 14:36 ` Eric Blake
2015-05-08 12:43 ` [Qemu-devel] [PATCH 3/4] migration: Add myself to the copyright list of both files Juan Quintela
2015-05-08 14:37 ` Eric Blake
2015-05-08 12:43 ` [Qemu-devel] [PATCH 4/4] movement: reduce include files Juan Quintela
2015-05-08 14:39 ` Eric Blake
2015-05-27 9:18 ` 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=1431088998-27721-1-git-send-email-quintela@redhat.com \
--to=quintela@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).