From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] include qemu-kvm.h at all cases.
Date: Tue, 17 Feb 2009 18:00:25 +0000 [thread overview]
Message-ID: <499AFB39.9000604@redhat.com> (raw)
In-Reply-To: <1234470982-330-1-git-send-email-glommer@redhat.com>
Glauber Costa 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?
>
Applied, thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] include qemu-kvm.h at all cases.
Date: Tue, 17 Feb 2009 18:00:25 +0000 [thread overview]
Message-ID: <499AFB39.9000604@redhat.com> (raw)
In-Reply-To: <1234470982-330-1-git-send-email-glommer@redhat.com>
Glauber Costa 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?
>
Applied, thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-02-17 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 20:36 [PATCH] include qemu-kvm.h at all cases Glauber Costa
2009-02-12 20:36 ` [Qemu-devel] " Glauber Costa
2009-02-17 0:01 ` Dustin Kirkland
2009-02-17 0:01 ` [Qemu-devel] " Dustin Kirkland
2009-02-17 18:00 ` Avi Kivity [this message]
2009-02-17 18:00 ` 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=499AFB39.9000604@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.