From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Fix volume keys not releasing for Pegatron platform
Date: Wed, 21 Apr 2010 17:36:38 +0000 [thread overview]
Message-ID: <20100421173638.GF3210@piware.de> (raw)
In-Reply-To: <1271870377.1674.5.camel@laptop>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Hello Jerone,
Jerone Young [2010-04-21 12:19 -0500]:
> Pegatron has a new platform coming out being sold by many small
> manufacturers. This platform has volume keys that are not sending a key
> release. This patch ensures those keys send release.
Thanks! Pushed.
<random rumble>This "common-volume-keys" is still a mystery to me --
if all those vendors can agree to a common set of broken volume keys,
why can't they agree to common scan codes for everything else???
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-04-21 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 17:19 [PATCH] Fix volume keys not releasing for Pegatron platform Jerone Young
2010-04-21 17:36 ` Martin Pitt [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=20100421173638.GF3210@piware.de \
--to=martin.pitt@ubuntu.com \
--cc=linux-hotplug@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).