From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: klondike <franxisco1988@gmail.com>,
Nikola Ciprich <extmaillist@linuxbox.cz>,
kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] qemu-kvm: Fix non-PCI target build
Date: Sun, 27 Feb 2011 13:35:43 +0200 [thread overview]
Message-ID: <4D6A370F.6070507@redhat.com> (raw)
In-Reply-To: <4D64C545.3020205@siemens.com>
On 02/23/2011 10:28 AM, Jan Kiszka wrote:
> Replace obsolete qemu-kvm.h with kvm.h in pci.c and build that module
> just like upstream does. This fixes non-x86 targets which have no PCI
> support.
Thanks, applied to mainline and stable-0.14.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-02-27 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 17:14 [ANNOUNCE] qemu-kvm-0.14.0 Avi Kivity
2011-02-23 7:49 ` Nikola Ciprich
2011-02-23 8:05 ` klondike
2011-02-23 8:16 ` Nikola Ciprich
2011-02-23 8:29 ` Nikola Ciprich
2011-02-23 8:39 ` klondike
2011-04-29 8:59 ` Bharat Bhushan
2011-02-23 8:28 ` [PATCH] qemu-kvm: Fix non-PCI target build Jan Kiszka
2011-02-23 8:37 ` klondike
2011-02-27 11:35 ` Avi Kivity [this message]
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=4D6A370F.6070507@redhat.com \
--to=avi@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=franxisco1988@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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).