From: Ulrich Drepper <drepper@akkadia.org>
To: arnd@arndb.de, davem@davemloft.net, hverkuil@xs4all.nl,
laurent.pinchart@ideasonboard.com, linux-kernel@vger.kernel.org,
mchehab@redhat.com
Subject: [PATCH] Install kernel-page-flags.h
Date: Wed, 14 Mar 2012 03:26:07 -0400 [thread overview]
Message-ID: <201203140726.q2E7Q73i021607@drepperk.user.openhosting.com> (raw)
Programs using /proc/kpageflags need to know about the various flags. The
<linux/kernel-page-flags.h> provides them and the comments in the file
indicate that it is supposed to be used by user-level code. But the file
is not installed.
The patch below installs the headers and marks the unstable flags as
out-of-bounds.
Signed-off-by: Ulrich Drepper <drepper@gmail.com>
include/linux/Kbuild | 1 +
include/linux/kernel-page-flags.h | 4 ++++
2 files changed, 5 insertions(+)
diff --git a/include/linux/Kbuild b/include/linux/Kbuild
index c94e717..356928e 100644
--- a/include/linux/Kbuild
+++ b/include/linux/Kbuild
@@ -227,6 +227,7 @@ header-y += kd.h
header-y += kdev_t.h
header-y += kernel.h
header-y += kernelcapi.h
+header-y += kernel-page-flags.h
header-y += keyboard.h
header-y += keyctl.h
header-y += l2tp.h
diff --git a/include/linux/kernel-page-flags.h b/include/linux/kernel-page-flags.h
index bd92a89..096b05d 100644
--- a/include/linux/kernel-page-flags.h
+++ b/include/linux/kernel-page-flags.h
@@ -31,6 +31,8 @@
#define KPF_KSM 21
+#ifdef __KERNEL__
+
/* kernel hacking assistances
* WARNING: subject to change, never rely on them!
*/
@@ -43,4 +45,6 @@
#define KPF_ARCH 38
#define KPF_UNCACHED 39
+#endif /* __KERNEL__ */
+
#endif /* LINUX_KERNEL_PAGE_FLAGS_H */
next reply other threads:[~2012-03-14 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 7:26 Ulrich Drepper [this message]
2012-03-14 7:58 ` Christoph Hellwig
2012-03-14 8:03 ` Ulrich Drepper
2012-03-14 10:40 ` Alexey Dobriyan
2012-03-19 11:32 ` Christoph Hellwig
2012-03-19 12:45 ` Alexey Dobriyan
2012-03-25 12:28 ` Ulrich Drepper
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=201203140726.q2E7Q73i021607@drepperk.user.openhosting.com \
--to=drepper@akkadia.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®