From: Avi Kivity <avi@qumranet.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: Bill Davidsen <davidsen@tmr.com>, KVM list <kvm@vger.kernel.org>,
nikola.ciprich@linuxbox.cz
Subject: Re: [PATH] kvm-72 - fix compilation on 2.6.26 (anon_inode_getfd flag)
Date: Wed, 30 Jul 2008 17:34:14 +0300 [thread overview]
Message-ID: <48907BE6.1090607@qumranet.com> (raw)
In-Reply-To: <20080729204932.GA4791@localhost.localdomain>
Nikola Ciprich wrote:
>> Should that be ">=" for future use?
>>
> nope, newer versions have also the flag parameter (see 2.6.27-rcX), so this is intended only for 2.6.26
>
>
Please resend the patch as I don't have it in my mailbox.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-07-30 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 8:55 [PATH] kvm-72 - fix compilation on 2.6.26 (anon_inode_getfd flag) Nikola Ciprich
2008-07-29 20:26 ` Bill Davidsen
2008-07-29 20:49 ` Nikola Ciprich
2008-07-30 14:34 ` Avi Kivity [this message]
2008-07-30 16:10 ` Nikola Ciprich
2008-07-31 10:56 ` 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=48907BE6.1090607@qumranet.com \
--to=avi@qumranet.com \
--cc=davidsen@tmr.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--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