From: Jan Kiszka <jan.kiszka@web.de>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kgdb-bugreport@lists.sourceforge.net
Subject: [PATCH] KGDB: kconfig polishing
Date: Thu, 07 Feb 2008 08:38:35 +0100 [thread overview]
Message-ID: <47AAB57B.2010709@web.de> (raw)
Just for the sake of cleanness.
Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
---
lib/Kconfig.kgdb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: b/lib/Kconfig.kgdb
===================================================================
--- a/lib/Kconfig.kgdb
+++ b/lib/Kconfig.kgdb
@@ -16,7 +16,7 @@ config KGDB_ARCH_HAS_SHADOW_INFO
depends on KGDB
config KGDB_CONSOLE
- bool "KGDB: Console messages through gdb"
+ bool "Console messages through gdb"
depends on KGDB
help
If you say Y here, console messages will appear through gdb.
@@ -53,7 +53,7 @@ config KGDB_8250
used by the standard 8250 driver or serial earlyprintk/earlycon.
config KGDBOC
- tristate "KGDB: Share serial console and kgdb port"
+ tristate "Shared serial console and kgdb port"
depends on KGDB
select SERIAL_POLL
select MAGIC_SYSRQ
reply other threads:[~2008-02-07 7:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47AAB57B.2010709@web.de \
--to=jan.kiszka@web.de \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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