From: Paul Mundt <lethal@linux-sh.org>
To: Roland Dreier <rolandd@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] net: trivial MLX4_DEBUG dependency fix.
Date: Thu, 10 May 2007 12:50:28 +0900 [thread overview]
Message-ID: <20070510035028.GA26453@linux-sh.org> (raw)
First SLUB_DEBUG, and now this..
CONFIG_MLX4_DEBUG works out to a def_bool y for those that
have CONFIG_EMBEDDED set. Make it depend on MLX4_CORE..
I'll let someone else wonder why debugging output is default enabled,
this seems to be a worrying trend as of late.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
--
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index fa489b1..b3f4ffa 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -2500,6 +2500,7 @@ config MLX4_CORE
config MLX4_DEBUG
bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
+ depends on MLX4_CORE
default y
---help---
This option causes debugging code to be compiled into the
next reply other threads:[~2007-05-10 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 3:50 Paul Mundt [this message]
2007-05-10 11:42 ` [PATCH] net: trivial MLX4_DEBUG dependency fix Roland Dreier
2007-05-10 12:11 ` Satyam Sharma
2007-05-10 18:20 ` Roland Dreier
2007-05-10 12:49 ` Paul Mundt
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=20070510035028.GA26453@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rolandd@cisco.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