From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make Dell keyboard repeat quirk apply to a wider range of hardware
Date: Fri, 15 Aug 2008 15:04:44 -0400 [thread overview]
Message-ID: <20080815150420.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20080814033255.GA21721@srcf.ucam.org>
On Thu, Aug 14, 2008 at 04:32:55AM +0100, Matthew Garrett wrote:
> Dell laptops fail to send key up events for several of their special
> keys. There's an existing quirk in the kernel to handle this, but it's
> limited to the Latitude range. This patch extends it to cover all
> portable Dells.
>
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
>
Applied to 'next', thank you Matthew.
--
Dmitry
prev parent reply other threads:[~2008-08-15 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 3:32 [PATCH] Make Dell keyboard repeat quirk apply to a wider range of hardware Matthew Garrett
2008-08-14 4:50 ` legolas558
2008-08-14 11:15 ` Matthew Garrett
2008-08-15 19:04 ` 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=20080815150420.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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).