* [PATCH] use "#ifdef __KERNEL" to avoid compile error in input.h
@ 2006-04-07 6:03 Luke Yang
0 siblings, 0 replies; only message in thread
From: Luke Yang @ 2006-04-07 6:03 UTC (permalink / raw)
To: Andrew Morton, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Hi all,
In linux/input.h, struct input_device_id uses type kernel_ulong_t,
which is defined in linux/mod_devicetable.h, but which is only
included when __KERNEL__ is defined. So struct input_device_id should
also be exported only in kernel mode.
Signed-off-by: Luke Yang <luke.adi@gmail.com>
diff --git a/include/linux/input.h b/include/linux/input.h
index b0e612d..0319b65 100644
--- a/include/linux/input.h
+++ b/include/linux/input.h
@@ -805,6 +805,7 @@ #define FF_AUTOCENTER 0x61
#define FF_MAX 0x7f
+#ifdef __KERNEL__
struct input_device_id {
kernel_ulong_t flags;
@@ -823,6 +824,7 @@ struct input_device_id {
kernel_ulong_t driver_info;
};
+#endif
/*
* Structure for hotplug & device<->driver matching.
Best regards,
Luke Yang, Blackfin Linux kernel maintainer
luke.adi@gmail.com
[-- Attachment #2: correct_kernel_mode_define_of_input_h.patch --]
[-- Type: text/x-patch, Size: 438 bytes --]
diff --git a/include/linux/input.h b/include/linux/input.h
index b0e612d..0319b65 100644
--- a/include/linux/input.h
+++ b/include/linux/input.h
@@ -805,6 +805,7 @@ #define FF_AUTOCENTER 0x61
#define FF_MAX 0x7f
+#ifdef __KERNEL__
struct input_device_id {
kernel_ulong_t flags;
@@ -823,6 +824,7 @@ struct input_device_id {
kernel_ulong_t driver_info;
};
+#endif
/*
* Structure for hotplug & device<->driver matching.
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2006-04-07 6:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-04-07 6:03 [PATCH] use "#ifdef __KERNEL" to avoid compile error in input.h Luke Yang
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).