From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
LKML <linux-kernel@vger.kernel.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [patch resend] zaurus keyboard driver updates
Date: Tue, 14 Mar 2006 00:28:54 -0500 [thread overview]
Message-ID: <200603140028.54431.dtor_core@ameritech.net> (raw)
In-Reply-To: <1141552270.6521.5.camel@localhost.localdomain>
On Sunday 05 March 2006 04:51, Richard Purdie wrote:
> Zaurus keyboard driver updates:
> * Change the scan interval from 100ms to 50ms. This stops the key
> repeat from triggering on double letter presses.
> * Remove unneeded stale hinge code from corgikbd
> * Change unneeded corgi GPIO pins to inputs when suspended
> * Add support for the headphone jack switch for both corgi and spitz
> (as switch SW_2)
>
> Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
>
Applied to the input tree, thank you Richard.
--
Dmitry
prev parent reply other threads:[~2006-03-14 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 9:51 [patch resend] zaurus keyboard driver updates Richard Purdie
2006-03-14 5:28 ` Dmitry Torokhov [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=200603140028.54431.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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