From: Jason Wessel <jason.wessel@windriver.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: torvalds@linux-foundation.org,
kgdb-bugreport@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [RESEND] Re: [Kgdb-bugreport] [GIT PULL] V2 kdb / early debug (1 of 2) for 2.6.34
Date: Mon, 22 Mar 2010 15:13:07 -0500 [thread overview]
Message-ID: <4BA7CF53.7040504@windriver.com> (raw)
In-Reply-To: <20100322130530.50e8de1e@jbarnes-piketon>
On 03/22/2010 03:05 PM, Jesse Barnes wrote:
> 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.
>
>
I worked with Dmitry Torokhov to come to some agreement with respect to
the kdb keyboard handling. This resulted in dropping one of the
keyboard patches entirely, and it will be done another way. There are
RFC patches from me on this, as well as Dmitry's own RFC patches for
sysrq handling.
The discussion with Dmitry also resulted in the cleanup of the current
kdb low level PS/2 kdb keyboard driver to an acceptable state. I was
waiting to hear back on the response to the pull request before
investing further effort here. I am always open to suggestions of how
to solve this tricky problem.
Thanks,
Jason.
next prev parent reply other threads:[~2010-03-22 20:13 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 ` [Kgdb-bugreport] " Jason Wessel
2010-03-21 2:14 ` [RESEND] " Jason Wessel
2010-03-22 20:05 ` Jesse Barnes
2010-03-22 20:13 ` Jason Wessel [this message]
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=4BA7CF53.7040504@windriver.com \
--to=jason.wessel@windriver.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--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