From: Jan Kiszka <jan.kiszka@web.de>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: [PATCH] KGDB: refactor kconfig menu
Date: Tue, 29 Jan 2008 00:01:35 +0100 [thread overview]
Message-ID: <479E5ECF.2000302@web.de> (raw)
In-Reply-To: <479E5C18.4010809@web.de>
Jan Kiszka wrote:
> Jan Kiszka wrote:
>> This is an attempt to improve the so far, well, unfortunate Kconfig menu
>> organization of KGDB. Most notably, it pushes all sub-entries into their
>> own menuconfig, removes the (IMHO) unneeded "Method for KGDB
>> communication" choice, and ensures everything is indented properly. This
>> should keep the original semantic while reducing the number of knobs the
>> user is confronted with.
>
> I realized that KGDB_8250_CONF_STRING is unused in case the driver is
> built as module. So here comes an updated patch that exposes this option
> only when it is actually needed.
Oh, I missed that part one is already in x86.git. So the delta is:
Ask for KGDB_8250_CONF_STRING only in the non-modular case.
Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
---
lib/Kconfig.kgdb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/lib/Kconfig.kgdb
===================================================================
--- a/lib/Kconfig.kgdb
+++ b/lib/Kconfig.kgdb
@@ -55,7 +55,7 @@ config KGDB_PORT_NUM
config KGDB_8250_CONF_STRING
string "Configuration string for KGDB"
- depends on KGDB_8250 && !KGDB_SIMPLE_SERIAL
+ depends on (KGDB_8250 = y) && !KGDB_SIMPLE_SERIAL
default "io,2f8,115200,3" if X86
help
The format of this string should be <io or mmio>,
prev parent reply other threads:[~2008-01-28 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 15:48 [PATCH] KGDB: refactor kconfig menu Jan Kiszka
2008-01-27 18:01 ` Jason Wessel
2008-01-27 18:15 ` Jan Kiszka
2008-01-28 22:50 ` Jan Kiszka
2008-01-28 23:01 ` Jan Kiszka [this message]
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=479E5ECF.2000302@web.de \
--to=jan.kiszka@web.de \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.