From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] create kvm-shared-all.c and kvm-shared.h
Date: Tue, 09 Jun 2009 19:42:01 +0300 [thread overview]
Message-ID: <4A2E90D9.60908@redhat.com> (raw)
In-Reply-To: <20090609163906.GO11966@poweredge.glommer>
Glauber Costa wrote:
>> Yes, we could simply append libkvm-all.c and qemu-kvm.c to kvm-all.c,
>> and gradually include more of kvm-all.c as we delete parts of libkvm.c
>> and qemu-kvm.c.
>>
> I tried it myself, and it generates tons of conflicts. So scary.
> I'd prefer to do it in the way I propose, until there is nothing left on kvm-all.c
>
There shouldn't be any conflicts, kvm-all is ifdefed out.
We'd enable bits one by one until everything is enabled.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-09 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 16:04 [Qemu-devel] [PATCH] create kvm-shared-all.c and kvm-shared.h Glauber Costa
2009-06-09 16:17 ` [Qemu-devel] " Jan Kiszka
2009-06-09 16:26 ` Avi Kivity
2009-06-09 16:39 ` Glauber Costa
2009-06-09 16:42 ` Avi Kivity [this message]
2009-06-09 16:42 ` Jan Kiszka
2009-06-09 16:51 ` Glauber Costa
2009-06-09 16:51 ` Jan Kiszka
2009-06-09 16:37 ` Glauber Costa
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=4A2E90D9.60908@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@redhat.com \
--cc=jan.kiszka@siemens.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).