From: akpm@linux-foundation.org
To: sonic.zhang@analog.com, alan@lxorguk.ukuu.org.uk,
stable@kernel.org, vapier@gentoo.org, mm-commits@vger.kernel.org
Subject: [merged] serial-bfin_5xx-kgdboc-should-accept-gdb-break-only-when-it-is-active.patch removed from -mm tree
Date: Fri, 29 Jan 2010 12:16:53 -0800 [thread overview]
Message-ID: <201001292016.o0TKGrm2003267@imap1.linux-foundation.org> (raw)
The patch titled
serial: bfin_5xx: kgdboc should accept gdb break only when it is active
has been removed from the -mm tree. Its filename was
serial-bfin_5xx-kgdboc-should-accept-gdb-break-only-when-it-is-active.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: serial: bfin_5xx: kgdboc should accept gdb break only when it is active
From: Sonic Zhang <sonic.zhang@analog.com>
If we always check for gdb breaks even when it isn't active, we get false
positives on normal code and the system panics.
URL: http://blackfin.uclinux.org/gf/tracker/5277
Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/serial/bfin_5xx.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN drivers/serial/bfin_5xx.c~serial-bfin_5xx-kgdboc-should-accept-gdb-break-only-when-it-is-active drivers/serial/bfin_5xx.c
--- a/drivers/serial/bfin_5xx.c~serial-bfin_5xx-kgdboc-should-accept-gdb-break-only-when-it-is-active
+++ a/drivers/serial/bfin_5xx.c
@@ -237,7 +237,8 @@ static void bfin_serial_rx_chars(struct
#if defined(CONFIG_KGDB_SERIAL_CONSOLE) || \
defined(CONFIG_KGDB_SERIAL_CONSOLE_MODULE)
- if (kgdb_connected && kgdboc_port_line == uart->port.line)
+ if (kgdb_connected && kgdboc_port_line == uart->port.line
+ && kgdboc_break_enabled)
if (ch == 0x3) {/* Ctrl + C */
kgdb_breakpoint();
return;
_
Patches currently in -mm which might be from sonic.zhang@analog.com are
linux-next.patch
reply other threads:[~2010-01-29 20:18 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=201001292016.o0TKGrm2003267@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sonic.zhang@analog.com \
--cc=stable@kernel.org \
--cc=vapier@gentoo.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 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.