public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: torvalds@linux-foundation.org
Cc: kgdb-bugreport@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Kgdb-bugreport] [GIT PULL] V2 kdb / early debug (1 of 2) for 2.6.34
Date: Mon, 15 Mar 2010 08:26:57 -0500	[thread overview]
Message-ID: <4B9E35A1.9080609@windriver.com> (raw)
In-Reply-To: <1267420188-10227-1-git-send-email-jason.wessel@windriver.com>

On 02/28/2010 11:09 PM, Jason Wessel wrote:
> Linus please pull the kdb-merge tree which merges the kdb front end
> into the kernel debug core for 7 architectures.
> 

Linus, what is the status of the kdb & early debug pull requests?

I had not seen anything merged yet and you listed these as requiring
further review in your -rc1 message.  Are there any questions I can
answer?

I would like to know how to proceed because there were a number of
kgdb specific fixes integrated into the first part of the kdb merge,
as well as the directory reorganization (split of the debug core and
the gdbstub).  I have several minor non-x86 kgdb fixes waiting against
the new directory structure.

Thanks,
Jason


  reply	other threads:[~2010-03-15 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01  5:09 [GIT PULL] V2 kdb / early debug (1 of 2) for 2.6.34 Jason Wessel
2010-03-15 13:26 ` Jason Wessel [this message]
2010-03-21  2:14 ` [RESEND] Re: [Kgdb-bugreport] " Jason Wessel
2010-03-22 20:05   ` Jesse Barnes
2010-03-22 20:13     ` Jason Wessel
2010-03-22 21:26       ` Dmitry Torokhov

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=4B9E35A1.9080609@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