From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Linux-Input <linux-input@atrey.karlin.mff.cuni.cz>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix spitzkbd suspend key handling
Date: Thu, 3 Jan 2008 11:16:02 -0500 [thread overview]
Message-ID: <d120d5000801030816o697219d8h664b2823e1965cfc@mail.gmail.com> (raw)
In-Reply-To: <1199233037.4653.44.camel@localhost.localdomain>
On Jan 1, 2008 7:17 PM, Richard Purdie <rpurdie@rpsys.net> wrote:
> The spitz keyboard driver reports KEY_SUSPEND events but doesn't
> register its use of this event in the keybit bitfield, breaking input
> events for this key. This patch fixes that by registering the key in the
> keybit bitfield.
>
Applied to my tree - for-linus branch. Thank you Richard.
--
Dmitry
P.S. Try to migrate to linux-input@vger, I'd like to get off atrey server
parent reply other threads:[~2008-01-03 16:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1199233037.4653.44.camel@localhost.localdomain>]
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=d120d5000801030816o697219d8h664b2823e1965cfc@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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).