From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] qemu-kvm: kvm headers update
Date: Tue, 06 Oct 2009 11:51:45 +0200 [thread overview]
Message-ID: <4ACB1331.7060505@redhat.com> (raw)
In-Reply-To: <20091005192720.GA3399@redhat.com>
On 10/05/2009 09:27 PM, Michael S. Tsirkin wrote:
>
>
>> Why are you dropping these? Any dependencies on CONFIG_ will be broken.
>>
> Instead I included kvm_types which has these.
>
Oh, a side effect. Mind moving the CONFIG_* stuff to a separate header
(which we can include using -include)? Separate patch please.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-06 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 9:46 [PATCH] qemu-kvm: kvm headers update Michael S. Tsirkin
2009-10-05 15:38 ` Avi Kivity
2009-10-05 19:27 ` Michael S. Tsirkin
2009-10-06 9:51 ` Avi Kivity [this message]
2009-10-06 9:52 ` Avi Kivity
2009-10-06 17:18 ` Michael S. Tsirkin
[not found] ` <200910061909.29977.arnd@arndb.de>
2009-10-08 13:39 ` Avi Kivity
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=4ACB1331.7060505@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@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).