From: Jason Wessel <jason.wessel@windriver.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: kgdb-bugreport@lists.sourceforge.net,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] input / sysrq fixes for use with kdb
Date: Wed, 27 Oct 2010 07:53:14 -0500 [thread overview]
Message-ID: <4CC820BA.3000203@windriver.com> (raw)
In-Reply-To: <20101010211944.GB27553@core.coreip.homeip.net>
On 10/10/2010 04:19 PM, Dmitry Torokhov wrote:
> On Thu, Oct 07, 2010 at 03:35:45PM -0500, Jason Wessel wrote:
>
>> The goal of this patch set is to help eliminate the problems of
>> resuming from the kernel debugger and having "stuck keys".
>>
>> I am completely open to moving the code chunks around if it makes more
>> sense to put the function in the input.c.
>>
>> I had posted the first patch in the series before and never received
>> an ack or acceptance into the linux-input merge queue.
>>
>>
>
> Jason,
>
> I am aware of the problem however I am not quite happy with the proposed
> solution yet. Let me mull it over for a bit and I will get back to you.
>
Ping :-)
The merge window for 2.6.37 is almost over, and I would really like to
fix this or make it better than it is today, given that remainder of the
atomic KMS API is now merged in 2.6.37.
Thanks,
Jason.
prev parent reply other threads:[~2010-10-27 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 20:35 [PATCH 0/3] input / sysrq fixes for use with kdb Jason Wessel
2010-10-07 20:35 ` [PATCH 1/3] keyboard,kgdboc: Allow key release on kernel resume Jason Wessel
2010-10-07 20:35 ` [PATCH 2/3] keyboard,kdb: inject SYN events in kbd_clear_keys_helper Jason Wessel
2010-10-07 20:35 ` [PATCH 3/3] sysrq,keyboard: properly deal with alt-sysrq in sysrq input filter Jason Wessel
2010-10-10 21:19 ` [PATCH 0/3] input / sysrq fixes for use with kdb Dmitry Torokhov
2010-10-27 12:53 ` Jason Wessel [this message]
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=4CC820BA.3000203@windriver.com \
--to=jason.wessel@windriver.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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