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/kdb tree for 2.6.39-rc1
Date: Fri, 25 Mar 2011 16:44:16 -0500	[thread overview]
Message-ID: <1301089460-1936-1-git-send-email-jason.wessel@windriver.com> (raw)

Linus, please pull the for_linus branch to pick up the minor clean ups
for kgdb for 2.6.39.

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

Thanks,
Jason.

---
The following changes since commit 4bbba111d94781d34081c37856bbc5eb33f6c72a:

  Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6 (2011-03-23 07:58:09 -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

Dan Carpenter (1):
      kgdboc,kgdbts: strlen() doesn't count the terminator

Jason Wessel (1):
      kgdb,x86_64: fix compile warning found with sparse

Jovi Zhang (1):
      kdb: code cleanup to use macro instead of value

Namhyung Kim (1):
      kdb: add usage string of 'per_cpu' command

 arch/x86/kernel/kgdb.c      |    4 ++--
 drivers/misc/kgdbts.c       |    2 +-
 drivers/tty/serial/kgdboc.c |    2 +-
 kernel/debug/kdb/kdb_main.c |    4 ++--
 4 files changed, 6 insertions(+), 6 deletions(-)

             reply	other threads:[~2011-03-25 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 21:44 Jason Wessel [this message]
2011-03-25 21:44 ` [PATCH 1/4] kgdboc,kgdbts: strlen() doesn't count the terminator Jason Wessel
2011-03-25 21:44 ` [PATCH 2/4] kdb: code cleanup to use macro instead of value Jason Wessel
2011-03-25 21:44 ` [PATCH 3/4] kgdb,x86_64: fix compile warning found with sparse Jason Wessel
2011-03-25 21:44 ` [PATCH 4/4] kdb: add usage string of 'per_cpu' command 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=1301089460-1936-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®