From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [dell-wmi] Dell Vostro 3360 extra multimedia keys don't work
Date: Tue, 15 Apr 2014 01:08:40 +0300 [thread overview]
Message-ID: <1537483.s6VfFnerp0@spock> (raw)
In-Reply-To: <20140414220500.GA26495@srcf.ucam.org>
Could I help somehow else? Any extra dumps needed?
On Monday 14 April 2014 23:05:00 Matthew Garrett wrote:
> On Tue, Apr 15, 2014 at 01:03:44AM +0300, Oleksandr Natalenko wrote:
> > They both report "e0f0".
>
> Well bother. In that case there must be some other way to distinguish
> them. I'll look into it.
--
Oleksandr post-factum Natalenko, MSc
pf-kernel community
https://natalenko.name/
prev parent reply other threads:[~2014-04-14 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 21:29 [dell-wmi] Dell Vostro 3360 extra multimedia keys don't work Oleksandr Natalenko
2014-04-14 21:33 ` Matthew Garrett
2014-04-14 21:37 ` Oleksandr Natalenko
2014-04-14 21:57 ` Matthew Garrett
2014-04-14 22:03 ` Oleksandr Natalenko
2014-04-14 22:05 ` Matthew Garrett
2014-04-14 22:08 ` Oleksandr Natalenko [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=1537483.s6VfFnerp0@spock \
--to=oleksandr@natalenko.name \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@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