From: Paul Bolle <pebolle@tiscali.nl>
To: David Howells <dhowells@redhat.com>,
Koichi Yasutake <yasutake.koichi@jp.panasonic.com>
Cc: Richard Weinberger <richard@nod.at>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-am33-list@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH 1/5] MN10300: Remove Kconfig symbol GDBSTUB
Date: Thu, 18 Sep 2014 20:31:59 +0200 [thread overview]
Message-ID: <1411065119.2017.73.camel@x220> (raw)
Commit 1a8d59e529d0 ("MN10300: Deprecate gdbstub") made the Kconfig
symbol GDBSTUB depend on DEPRECATED. Since that Kconfig symbol doesn't
exist, this Kconfig entry has been dead since v2.6.39. Remove it.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
---
arch/mn10300/Kconfig.debug | 15 ---------------
1 file changed, 15 deletions(-)
diff --git a/arch/mn10300/Kconfig.debug b/arch/mn10300/Kconfig.debug
index 94efb3ed223f..6a8c7e8d6156 100644
--- a/arch/mn10300/Kconfig.debug
+++ b/arch/mn10300/Kconfig.debug
@@ -30,21 +30,6 @@ config KPROBES
for kernel debugging, non-intrusive instrumentation and testing.
If in doubt, say "N".
-config GDBSTUB
- bool "Remote GDB kernel debugging"
- depends on DEBUG_KERNEL && DEPRECATED
- select DEBUG_INFO
- select FRAME_POINTER
- help
- If you say Y here, it will be possible to remotely debug the kernel
- using gdb. This enlarges your kernel ELF image disk size by several
- megabytes and requires a machine with more than 16 MB, better 32 MB
- RAM to avoid excessive linking time. This is only useful for kernel
- hackers. If unsure, say N.
-
- This is deprecated in favour of KGDB and will be removed in a later
- version.
-
config GDBSTUB_IMMEDIATE
bool "Break into GDB stub immediately"
depends on GDBSTUB
--
1.9.3
reply other threads:[~2014-09-18 18:32 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=1411065119.2017.73.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=yasutake.koichi@jp.panasonic.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