From: Jason Wessel <jason.wessel@windriver.com>
To: dmitry.torokhov@gmail.com
Cc: kgdb-bugreport@lists.sourceforge.net,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] input / sysrq fixes for use with kdb
Date: Thu, 7 Oct 2010 15:35:45 -0500 [thread overview]
Message-ID: <1286483748-1171-1-git-send-email-jason.wessel@windriver.com> (raw)
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.
Thanks,
Jason.
---
The following changes since commit cb655d0f3d57c23db51b981648e452988c0223f9:
Linus Torvalds (1):
Linux 2.6.36-rc7
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_input
Jason Wessel (2):
keyboard,kgdboc: Allow key release on kernel resume
sysrq,keyboard: properly deal with alt-sysrq in sysrq input filter
Maxim Levitsky (1):
keyboard,kdb: inject SYN events in kbd_clear_keys_helper
drivers/char/keyboard.c | 38 +++++++++++++++++++++++++++
drivers/char/sysrq.c | 64 +++++++++++++++++++++++++++++++++++++++++++--
drivers/serial/kgdboc.c | 13 +++++++++
include/linux/kbd_kern.h | 1 +
4 files changed, 113 insertions(+), 3 deletions(-)
next reply other threads:[~2010-10-07 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 20:35 Jason Wessel [this message]
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
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=1286483748-1171-1-git-send-email-jason.wessel@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;
as well as URLs for NNTP newsgroup(s).