Commit 4b5b4c7222 ("staging/lustre/libcfs: restore LINVRNT") added
"default false" to this Kconfig file. It was obviously meant to use
"default n" here.
Signed-off-by: Paul Bolle <pebo...@tiscali.nl>
---
0) Tested lightly, with "make menuconfig" only.
1) No-one noticed because "default <invalid Kconfig symbol>" and
"default n" behave the same. Actually, it seems "default n" isn't needed
at all. But there are hundreds of Kconfig symbols that use "default n",
so I suppose it serves some purpose.
drivers/staging/lustre/lustre/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/Kconfig
b/drivers/staging/lustre/lustre/Kconfig
index e0eb830..002dd2e 100644
--- a/drivers/staging/lustre/lustre/Kconfig
+++ b/drivers/staging/lustre/lustre/Kconfig
@@ -43,7 +43,7 @@ config LUSTRE_OBD_MAX_IOCTL_BUFFER
config LUSTRE_DEBUG_EXPENSIVE_CHECK
bool "Enable Lustre DEBUG checks"
depends on LUSTRE_FS
- default false
+ default n
help
This option is mainly for debug purpose. It enables Lustre code to do
expensive checks that may have a performance impact.
--
1.8.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
