From: Jason Wessel <jason.wessel@windriver.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <kgdb-bugreport@lists.sourceforge.net>
Subject: [GIT PULL] kgdb/kdb updates for 3.1
Date: Mon, 1 Aug 2011 14:00:56 -0500 [thread overview]
Message-ID: <1312225260-1028-1-git-send-email-jason.wessel@windriver.com> (raw)
Linus, please pull the for_linus branch to pick up the minor kgdb/kdb
cleanups accumulated in the last few months.
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_linus
Thanks,
Jason.
---
The following changes since commit 02f8c6aee8df3cdc935e9bdd4f2d020306035dbe:
Linux 3.0 (2011-07-21 19:17:23 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_linus
Jason Wessel (4):
kdb: cleanup unused variables missed in the original kdb merge
kdb,kgdb: Implement switch and pass buffer from kdb -> gdb
kdb: Remove all references to DOING_KGDB2
kdb,kgdb: Allow arbitrary kgdb magic knock sequences
kernel/debug/gdbstub.c | 22 +++++++++++++++-------
kernel/debug/kdb/kdb_bt.c | 5 ++---
kernel/debug/kdb/kdb_cmds | 4 ----
kernel/debug/kdb/kdb_debugger.c | 21 ++++++++-------------
kernel/debug/kdb/kdb_io.c | 36 +++++++++++++++++++++++++-----------
kernel/debug/kdb/kdb_main.c | 4 ++--
kernel/debug/kdb/kdb_private.h | 3 +--
7 files changed, 53 insertions(+), 42 deletions(-)
next reply other threads:[~2011-08-01 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 19:00 Jason Wessel [this message]
2011-08-01 19:00 ` [PATCH 1/4] kdb: cleanup unused variables missed in the original kdb merge Jason Wessel
2011-08-01 19:00 ` [PATCH 2/4] kdb,kgdb: Implement switch and pass buffer from kdb -> gdb Jason Wessel
2011-08-01 19:00 ` [PATCH 3/4] kdb: Remove all references to DOING_KGDB2 Jason Wessel
2011-08-01 19:01 ` [PATCH 4/4] kdb,kgdb: Allow arbitrary kgdb magic knock sequences Jason Wessel
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=1312225260-1028-1-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®