From: Peng Tao <bergwolf@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Paul Bolle <pebolle@tiscali.nl>,
Peng Tao <bergwolf@gmail.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Peng Tao <tao.peng@emc.com>
Subject: [PATCH] staging/lustre: fix Kconfig bool defaults
Date: Tue, 23 Jul 2013 00:41:30 +0800 [thread overview]
Message-ID: <1374511290-4883-1-git-send-email-bergwolf@gmail.com> (raw)
Should be y/n instead of true/false...
Reported-by: Paul Bolle <pebolle@tiscali.nl>
Cc: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Peng Tao <tao.peng@emc.com>
---
This applis on top of the 48 Intel tree ported patches.
drivers/staging/lustre/lustre/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/lustre/lustre/Kconfig b/drivers/staging/lustre/lustre/Kconfig
index 566d89d..d80a78f 100644
--- a/drivers/staging/lustre/lustre/Kconfig
+++ b/drivers/staging/lustre/lustre/Kconfig
@@ -50,7 +50,7 @@ config LUSTRE_OBD_MAX_IOCTL_BUFFER
config LUSTRE_DEBUG_LU_REF_CHECK
bool "Enable Lustre DEBUG object refcount checks"
depends on LUSTRE_FS
- default false
+ default n
help
This option is mainly for debug purpose. It enables Lustre code to track
references between objects.
@@ -60,7 +60,7 @@ config LUSTRE_DEBUG_LU_REF_CHECK
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.
@@ -70,4 +70,4 @@ config LUSTRE_DEBUG_EXPENSIVE_CHECK
config LUSTRE_TRANSLATE_ERRNOS
bool
depends on LUSTRE_FS && !X86
- default true
+ default y
--
1.7.9.5
next reply other threads:[~2013-07-22 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 16:41 Peng Tao [this message]
2013-07-22 17:33 ` [PATCH] staging/lustre: fix Kconfig bool defaults Sam Ravnborg
2013-07-23 20:50 ` Greg Kroah-Hartman
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=1374511290-4883-1-git-send-email-bergwolf@gmail.com \
--to=bergwolf@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=tao.peng@emc.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