The patch titled
Subject: kconfig.h: use already defined macros for IS_REACHABLE() define
has been removed from the -mm tree. Its filename was
kconfigh-use-already-defined-macros-for-is_reachable-define.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx>
Subject: kconfig.h: use already defined macros for IS_REACHABLE() define
For the same reason as commit 02d699f1f464 ("include/linux/kconfig.h: ese
macros which are already defined"), it is better to use macros
IS_BUILTIN() and IS_MODULE() for defining IS_REACHABLE().
Link: http://lkml.kernel.org/r/1465883938-25194-3-git-send-email-yamada.masahiro@xxxxxxxxxxxxx
Signed-off-by: Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx>
Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Cc: Michal Simek <michal.simek@xxxxxxxxxx>
Cc: Arnd Bergmann <arnd@xxxxxxxx>
Cc: Michal Marek <mmarek@xxxxxxx>
Cc: Nicolas Pitre <nicolas.pitre@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/kconfig.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN include/linux/kconfig.h~kconfigh-use-already-defined-macros-for-is_reachable-define include/linux/kconfig.h
--- a/include/linux/kconfig.h~kconfigh-use-already-defined-macros-for-is_reachable-define
+++ a/include/linux/kconfig.h
@@ -42,8 +42,8 @@
* This is similar to IS_ENABLED(), but returns false when invoked from
* built-in code when CONFIG_FOO is set to 'm'.
*/
-#define IS_REACHABLE(option) (config_enabled(option) || \
- (config_enabled(option##_MODULE) && __is_defined(MODULE)))
+#define IS_REACHABLE(option) (IS_BUILTIN(option) || \
+ (IS_MODULE(option) && __is_defined(MODULE)))
/*
* IS_ENABLED(CONFIG_FOO) evaluates to 1 if CONFIG_FOO is set to 'y' or 'm',
_
Patches currently in -mm which might be from yamada.masahiro@xxxxxxxxxxxxx are
tree-wide-replace-config_enabled-with-is_enabled.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
