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 fixes for 2.6.36-rc1
Date: Mon, 16 Aug 2010 16:06:24 -0500 [thread overview]
Message-ID: <1281992789-2471-1-git-send-email-jason.wessel@windriver.com> (raw)
Linus, please pull the for_linus branch which contains:
* Fixes for compilation/warning errors since the kdb/kms merge
* 1 run time fix for atomic kms where console_blanked was not saved
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_lin
us
Thanks,
Jason.
---
The following changes since commit da5cabf80e2433131bf0ed8993abc0f7ea618c73:
Linus Torvalds (1):
Linux 2.6.36-rc1
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_lin
us
Eric Miao (1):
arm,kgdb: fix GDB_MAX_REGS no longer used
Jason Wessel (3):
kdb: fix compile error without CONFIG_KALLSYMS
vt: fix regression warnings from KMS merge
vt,console,kdb: preserve console_blanked while in kdb
Namhyung Kim (1):
kgdb: add missing __percpu markup in arch/x86/kernel/kgdb.c
arch/arm/kernel/kgdb.c | 2 +-
arch/x86/kernel/kgdb.c | 2 +-
drivers/char/vt.c | 11 +++++++----
kernel/debug/kdb/kdb_private.h | 7 +++++++
kernel/debug/kdb/kdb_support.c | 4 ++--
5 files changed, 18 insertions(+), 8 deletions(-)
next reply other threads:[~2010-08-16 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 21:06 Jason Wessel [this message]
2010-08-16 21:06 ` [PATCH 1/5] kdb: fix compile error without CONFIG_KALLSYMS Jason Wessel
2010-08-16 21:06 ` [PATCH 2/5] kgdb: add missing __percpu markup in arch/x86/kernel/kgdb.c Jason Wessel
2010-08-16 21:06 ` [PATCH 3/5] arm,kgdb: fix GDB_MAX_REGS no longer used Jason Wessel
2010-08-16 21:06 ` [PATCH 4/5] vt: fix regression warnings from KMS merge Jason Wessel
2010-08-16 21:06 ` [PATCH 5/5] vt,console,kdb: preserve console_blanked while in kdb 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=1281992789-2471-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®