mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 fixes for 2.6.34-rc2
Date: Mon, 22 Mar 2010 14:17:21 -0500	[thread overview]
Message-ID: <1269285449-1424-1-git-send-email-jason.wessel@windriver.com> (raw)

Linus, please pull the kgdb-fixes for 2.6.34.  

git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git kgdb-fixes

Summary:
  * The first 2 patches are the gdbstub and debug core split from the kdb tree
  * The rest are the fixes cherry picked from the kdb pull request

The previous kdb pull will require a rebase if you accept the kgdb
fixes because there were patch splits that occurred to make this patch
set.

Thanks,
Jason.

---
The following changes since commit 220bf991b0366cc50a94feede3d7341fa5710ee4:
  Linus Torvalds (1):
        Linux 2.6.34-rc2

are available in the git repository at:

Jason Wessel (8):
      Move kernel/kgdb.c to kernel/debug/debug_core.c
      Separate the gdbstub from the debug core
      kgdb: eliminate kgdb_wait(), all cpus enter the same way
      kgdb: have ebin2mem call probe_kernel_write once
      kgdb,debug_core: Use atomic operators which use barriers
      kgdbts,sh: Add in breakpoint pc offset for superh
      debug_core: Turn off tracing while in the debugger
      MAINTAINERS: update kgdb, and debug_core info

 MAINTAINERS               |    5 +-
 drivers/misc/kgdbts.c     |    6 +
 include/linux/kgdb.h      |    1 +
 kernel/Makefile           |    2 +-
 kernel/debug/Makefile     |    5 +
 kernel/debug/debug_core.c |  848 ++++++++++++++++++++++
 kernel/debug/debug_core.h |   55 ++
 kernel/debug/gdbstub.c    |  934 ++++++++++++++++++++++++
 kernel/kgdb.c             | 1763 ---------------------------------------------
 9 files changed, 1853 insertions(+), 1766 deletions(-)
 create mode 100644 kernel/debug/Makefile
 create mode 100644 kernel/debug/debug_core.c
 create mode 100644 kernel/debug/debug_core.h
 create mode 100644 kernel/debug/gdbstub.c
 delete mode 100644 kernel/kgdb.c

             reply	other threads:[~2010-03-22 19:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 19:17 Jason Wessel [this message]
2010-03-22 19:17 ` [PATCH 1/8] Move kernel/kgdb.c to kernel/debug/debug_core.c Jason Wessel
2010-03-22 19:17   ` [PATCH 2/8] Separate the gdbstub from the debug core Jason Wessel
2010-03-22 19:17     ` [PATCH 3/8] kgdb: eliminate kgdb_wait(), all cpus enter the same way Jason Wessel
2010-03-22 19:17       ` [PATCH 4/8] kgdb: have ebin2mem call probe_kernel_write once Jason Wessel
2010-03-22 19:17         ` [PATCH 5/8] kgdb,debug_core: Use atomic operators which use barriers Jason Wessel
2010-03-22 19:17           ` [PATCH 6/8] kgdbts,sh: Add in breakpoint pc offset for superh Jason Wessel
2010-03-22 19:17             ` [PATCH 7/8] debug_core: Turn off tracing while in the debugger Jason Wessel
2010-03-22 19:17               ` [PATCH 8/8] MAINTAINERS: update kgdb, and debug_core info Jason Wessel
2010-03-29 14:01 ` [GIT PULL] kgdb fixes for 2.6.34-rc2 Jason Wessel
2010-04-01 16:04   ` Linus Torvalds
2010-04-02 18:38     ` 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=1269285449-1424-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

Powered by JetHome