From: Avi Kivity <avi@redhat.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: "Nikola Ciprich" <extmaillist@linuxbox.cz>,
"René Pfeiffer" <lynx@luchs.at>, "KVM list" <kvm@vger.kernel.org>,
nikola.ciprich@linuxbox.cz
Subject: Re: [PATCH kvm-kmod] build fix for !#defined IOMMU_CACHE
Date: Thu, 21 May 2009 10:46:45 +0300 [thread overview]
Message-ID: <4A1506E5.3080207@redhat.com> (raw)
In-Reply-To: <20090521061805.GQ20823@sequoia.sous-sol.org>
Chris Wright wrote:
> This should fix the build for kernels that don't have IOMMU_CACHE,
> IOMMU_CAP_CACHE_COHERENCY or iommu_domain_has_cap defined.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-21 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 17:48 kvm-86 fails to compile with "'IOMMU_CACHE' undeclared" René Pfeiffer
2009-05-20 20:30 ` Nikola Ciprich
2009-05-20 20:45 ` Nikola Ciprich
2009-05-21 5:33 ` Chris Wright
2009-05-21 6:18 ` [PATCH kvm-kmod] build fix for !#defined IOMMU_CACHE Chris Wright
2009-05-21 7:46 ` Avi Kivity [this message]
2009-05-22 7:51 ` kvm-86 fails to compile with "'IOMMU_CACHE' undeclared" René Pfeiffer
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=4A1506E5.3080207@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=lynx@luchs.at \
--cc=nikola.ciprich@linuxbox.cz \
/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).