From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: torvalds@linux-foundation.org,
kgdb-bugreport@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] Re: [Kgdb-bugreport] [GIT PULL] V2 kdb / early debug (1 of 2) for 2.6.34
Date: Mon, 22 Mar 2010 13:05:30 -0700 [thread overview]
Message-ID: <20100322130530.50e8de1e@jbarnes-piketon> (raw)
In-Reply-To: <4BA58100.2000104@windriver.com>
On Sat, 20 Mar 2010 21:14:24 -0500
Jason Wessel <jason.wessel@windriver.com> wrote:
> 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.
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git kdb-merge
> >
>
> What is the status of this pull request? Was some part of the process
> missed here that there has been no response on this pull request?
>
> Please let me know what is wrong here. I have a number of other fixes
> pending to the tree at this point.
>
> Would it be possible to merge part of the tree that is only related to
> kgdb, in particular the directory re-organization?
IIRC he still had some issues with the keyboard/input handling. We
discussed it briefly a couple of weeks ago and he was worried about
potential duplication.
This may all be slander though; if so hopefully he'll recover from his
email backlog and respond to this. :)
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-03-22 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 5:09 Jason Wessel
2010-03-15 13:26 ` [Kgdb-bugreport] " Jason Wessel
2010-03-21 2:14 ` [RESEND] " Jason Wessel
2010-03-22 20:05 ` Jesse Barnes [this message]
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=20100322130530.50e8de1e@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=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®