From: Avi Kivity <avi@redhat.com>
To: hamo.by@gmail.com
Cc: mtosatti@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: fix undeclared MAY_{READ,WRITE,ACCESS}
Date: Sun, 25 Dec 2011 11:53:31 +0200 [thread overview]
Message-ID: <4EF6F29B.4070107@redhat.com> (raw)
In-Reply-To: <1324705595-4035-1-git-send-email-hamo.by@gmail.com>
On 12/24/2011 07:46 AM, hamo.by@gmail.com wrote:
> From: Yang Bai <hamo.by@gmail.com>
>
> commit 08a95a511af91a2a6c42f2a8f13b99402a39e84b checks
> device assignment permission but forgot to include the
> definition of MAY_{READ,WRITE,ACCESS} in linux/fs.h
> Include it and this fix the build error here:
> http://buildbot.b1-systems.de/kvm/builders/i386/builds/401
>
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-25 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-24 5:46 [PATCH] KVM: fix undeclared MAY_{READ,WRITE,ACCESS} hamo.by
2011-12-25 9:53 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-24 5:22 Yang Bai
2011-12-24 5:26 ` Yang Bai
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=4EF6F29B.4070107@redhat.com \
--to=avi@redhat.com \
--cc=hamo.by@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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).