diff options
author | Johannes Berg <johannes@sipsolutions.net> | 2013-04-02 11:38:46 +0200 |
---|---|---|
committer | Johannes Berg <johannes@sipsolutions.net> | 2013-04-02 11:38:46 +0200 |
commit | e2e97add101ed02b5e316166a5b9b5a5ddab983b (patch) | |
tree | b5bfca70be725955042a3c9f960e460145225af2 /compat/include | |
parent | 6d3a7273cd40d69c14691f4f599544aae93055a6 (diff) |
always use included rfkill
This isn't really desirable, but for now fixes build on
some kernels.
What we really should do is rename all the rfkill to be
backport symbols, and use it only on kernels that didn't
have a usable rfkill. OTOH, on new kernels one may want
to use a backported rfkill if the base configuration
doesn't include it?
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Diffstat (limited to 'compat/include')
-rw-r--r-- | compat/include/linux/rfkill.h | 22 |
1 files changed, 0 insertions, 22 deletions
diff --git a/compat/include/linux/rfkill.h b/compat/include/linux/rfkill.h index d615ac9f..a67e13ee 100644 --- a/compat/include/linux/rfkill.h +++ b/compat/include/linux/rfkill.h @@ -2,31 +2,9 @@ #define __COMPAT_RFKILL_H #if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,31)) - #include_next <linux/rfkill.h> - #else - -#include <linux/compat-2.6.h> - -#undef CONFIG_RFKILL -#undef CONFIG_RFKILL_INPUT -#undef CONFIG_RFKILL_LEDS - -#ifdef CONFIG_RFKILL_BACKPORT -#define CONFIG_RFKILL 1 -#endif - -#ifdef CONFIG_RFKILL_BACKPORT_INPUT -#define CONFIG_RFKILL_INPUT -#endif - -#ifdef CONFIG_RFKILL_BACKPORT_LEDS -#define CONFIG_RFKILL_LEDS -#endif - #include <linux/rfkill_backport.h> - #endif #endif |