From: Avi Kivity <avi@redhat.com>
To: nathan binkert <nate@binkert.org>
Cc: kvm@vger.kernel.org
Subject: Re: Fix to issues with kvm.h and g++
Date: Wed, 18 Mar 2009 10:49:44 +0200 [thread overview]
Message-ID: <49C0B5A8.6030808@redhat.com> (raw)
In-Reply-To: <217accd40903172123s4da28d15pdc1c1d121f2a51db@mail.gmail.com>
nathan binkert wrote:
> I'm having trouble compiling C++ code that #includes <linux/kvm.h>.
> There was a patch several months back and a request for an update to
> that patch, though the latest kernels still do not seem to work
> correctly. Is this something that is on anyone's radar?
>
> http://www.mail-archive.com/kvm@vger.kernel.org/msg06423.html
>
There was no followup so the issue was dropped. If you send a patch
I'll apply it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-18 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 4:23 Fix to issues with kvm.h and g++ nathan binkert
2009-03-18 8:49 ` Avi Kivity [this message]
2009-03-18 20:19 ` nathan binkert
2009-03-19 9:48 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-11-02 22:39 Daniel Godás
2008-11-06 15:57 ` 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=49C0B5A8.6030808@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nate@binkert.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