From: Dustin Kirkland <kirkland@canonical.com>
To: Glauber Costa <glommer@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, avi@redhat.com
Subject: [Qemu-devel] Re: [PATCH] include qemu-kvm.h at all cases.
Date: Mon, 16 Feb 2009 18:01:20 -0600 [thread overview]
Message-ID: <d9c105ea0902161601p7f26513ftd9dbb4a7d38d91a2@mail.gmail.com> (raw)
In-Reply-To: <1234470982-330-1-git-send-email-glommer@redhat.com>
On 2/12/09, Glauber Costa <glommer@redhat.com> wrote:
> We don't have any kind of kvm support for linux-user targets,
> but conditionalizing the inclusion of kvm header make
> linux-user compilation break. And we don't have a reason to
> prevent that, do we?
Ack, again, same problem here. The lack of inclusion of this header
breaks the build of kvm-84 for the Ubuntu package.
:-Dustin
next prev parent reply other threads:[~2009-02-17 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 20:36 [Qemu-devel] [PATCH] include qemu-kvm.h at all cases Glauber Costa
2009-02-17 0:01 ` Dustin Kirkland [this message]
2009-02-17 18:00 ` [Qemu-devel] " 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=d9c105ea0902161601p7f26513ftd9dbb4a7d38d91a2@mail.gmail.com \
--to=kirkland@canonical.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--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).