From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
akpm <akpm@linux-foundation.org>
Cc: xen-devel@lists.xensource.com, Jeremy@smtp1.linux-foundation.org,
Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Tony Finch <dot@dotat.at>, LKML <linux-kernel@vger.kernel.org>,
virtualization@lists.osdl.org, linux-next@vger.kernel.org
Subject: [PATCH -next] xen: fix header export to userspace
Date: Sat, 13 Nov 2010 08:44:39 -0800 [thread overview]
Message-ID: <20101113084439.d21bd0f0.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101112130547.c2a3c2c1.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
scripts/headers_install.pl prevents "__user" from being exported
to userspace headers, so just use compiler.h to make sure that
__user is defined and avoid the error.
unifdef: linux-next-20101112/xx64/usr/include/xen/privcmd.h.tmp: 79: Premature EOF (#if line 33 depth 1)
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com (moderated for non-subscribers)
Cc: virtualization@lists.osdl.org
Cc: Tony Finch <dot@dotat.at>
---
include/xen/privcmd.h | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
--- linux-next-20101112.orig/include/xen/privcmd.h
+++ linux-next-20101112/include/xen/privcmd.h
@@ -34,13 +34,10 @@
#define __LINUX_PUBLIC_PRIVCMD_H__
#include <linux/types.h>
+#include <linux/compiler.h>
typedef unsigned long xen_pfn_t;
-#ifndef __user
-#define __user
-#endif
-
struct privcmd_hypercall {
__u64 op;
__u64 arg[5];
next parent reply other threads:[~2010-11-13 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101112130547.c2a3c2c1.sfr@canb.auug.org.au>
2010-11-13 16:44 ` Randy Dunlap [this message]
2010-11-15 10:23 ` [PATCH -next] xen: fix header export to userspace Tony Finch
2010-11-15 18:15 ` Jeremy Fitzhardinge
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=20101113084439.d21bd0f0.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Jeremy@smtp1.linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dot@dotat.at \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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