From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Nick Warne <nick@ukfsn.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make Dell keyboard repeat quirk apply to a wider range of hardware
Date: Wed, 12 Nov 2008 17:27:12 +0000 [thread overview]
Message-ID: <20081112172712.GA16382@srcf.ucam.org> (raw)
In-Reply-To: <20081112172429.674c4ff3@palantir.linicks.net>
On Wed, Nov 12, 2008 at 05:24:29PM +0000, Nick Warne wrote:
> But how you determine if these certain laptops produce a keypress
> release I don't know with having all of them at hand...
The quirk is only applied to a small number of keys which wouldn't want
autorepeat anyway, so it's pretty clearly harmless even if the hardware
works sanely.
> So it needs BOTH 'Dell Inc.' and 'Dell Computer Corporation' to cover
> these laptops (I guess), as per the info I got from people running
> dmidecode:
That's what the patch adds. I don't have appropriate hardware to test.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-11-12 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 7:47 [PATCH] Make Dell keyboard repeat quirk apply to a wider range of hardware Nick Warne
2008-11-12 13:14 ` Nick Warne
2008-11-12 16:45 ` Andreas Mohr
2008-11-12 16:56 ` Matthew Garrett
2008-11-12 17:24 ` Nick Warne
2008-11-12 17:27 ` Matthew Garrett [this message]
2008-11-12 17:40 ` Nick Warne
2008-11-12 17:41 ` Matthew Garrett
2008-11-15 12:32 ` Nick Warne
2008-12-29 11:36 ` Nick Warne
2008-12-29 14:29 ` [PATCH] Input: atkbd - broaden the Dell DMI signatures Matthew Garrett
2008-12-30 4:15 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2008-08-14 3:32 [PATCH] Make Dell keyboard repeat quirk apply to a wider range of hardware Matthew Garrett
2008-08-15 19:04 ` Dmitry Torokhov
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=20081112172712.GA16382@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@ukfsn.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