From: Andre Przywara <andre.przywara@arm.com>
To: Andrea Arcangeli <aarcange@redhat.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
Pavel Emelyanov <xemul@parallels.com>
Subject: [PATCH 1/2] userfaultfd: remove kernel header include from uapi header
Date: Tue, 22 Sep 2015 11:45:55 +0100 [thread overview]
Message-ID: <1442918756-17892-2-git-send-email-andre.przywara@arm.com> (raw)
In-Reply-To: <1442918756-17892-1-git-send-email-andre.przywara@arm.com>
As include/uapi/linux/userfaultfd.h is a user visible header file,
it should not include kernel-exclusive header files.
So trying to build the userfaultfd test program from the selftests
directory fails, since it contains a reference to linux/compiler.h.
As it turns out, that header is not really needed there, so we can
simply remove it to fix that issue.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
---
include/uapi/linux/userfaultfd.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/uapi/linux/userfaultfd.h b/include/uapi/linux/userfaultfd.h
index df0e09b..9057d7a 100644
--- a/include/uapi/linux/userfaultfd.h
+++ b/include/uapi/linux/userfaultfd.h
@@ -11,8 +11,6 @@
#include <linux/types.h>
-#include <linux/compiler.h>
-
#define UFFD_API ((__u64)0xAA)
/*
* After implementing the respective features it will become:
--
2.5.1
next prev parent reply other threads:[~2015-09-22 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 10:45 [PATCH 0/2] selftests/userfaultfd: fix build Andre Przywara
2015-09-22 10:45 ` Andre Przywara [this message]
2015-09-22 10:45 ` [PATCH 2/2] selftests/userfaultfd: improve syscall number definition Andre Przywara
2015-09-22 13:49 ` Shuah Khan
2015-09-22 14:06 ` Andrea Arcangeli
2015-09-22 17:15 ` Andre Przywara
2015-09-23 9:55 ` Michael Ellerman
2015-09-23 13:11 ` Andre Przywara
2015-09-24 2:04 ` Michael Ellerman
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=1442918756-17892-2-git-send-email-andre.przywara@arm.com \
--to=andre.przywara@arm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=xemul@parallels.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
all inboxes | Powered by JetHome®