From: "Pali Rohár" <pali.rohar@gmail.com>
To: Kyle Evans <kvans32@gmail.com>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: BUG: Fn keys not working on EliteBook 8460p after fabf85e3ca15d5b94058f391dac8df870cdd427a
Date: Sat, 13 Apr 2013 03:31:17 +0200 [thread overview]
Message-ID: <201304130331.18301@pali> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 443 bytes --]
Hello,
all Fn keys, wifi switch, web and mute buttons not working anymore
on my notebook HP EliteBook 8460p. I bisected git commit which
broke all above keys: fabf85e3ca15d5b94058f391dac8df870cdd427a
When I reverted that commit after reboot buttons started working
again. Can you fix it or revert that broken commit? This is
critical problem, which caused my notebook to be unusable...
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2013-04-13 1:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 1:31 Pali Rohár [this message]
2013-04-13 1:35 ` BUG: Fn keys not working on EliteBook 8460p after fabf85e3ca15d5b94058f391dac8df870cdd427a Matthew Garrett
2013-04-13 12:36 ` Kyle Evans
2013-04-13 16:21 ` Matthew Garrett
2013-04-13 17:39 ` Kyle Evans
2013-04-13 17:42 ` Matthew Garrett
2013-04-16 16:26 ` Matthew Garrett
2013-04-17 13:56 ` Pali Rohár
2013-04-17 15:37 ` Kyle Evans
2013-04-17 17:59 ` Matthew Garrett
2013-04-17 18:55 ` Kyle Evans
2013-04-18 13:55 ` Kyle Evans
2013-04-18 15:58 ` Matthew Garrett
2013-04-18 16:48 ` Kyle Evans
2013-04-18 16:53 ` Matthew Garrett
2013-08-14 8:19 ` BUG: Again: Fn keys not working on EliteBook 8460p after b253c9d1d858a3f115f791ee4fe2b9399ae7dbbd Pali Rohár
2013-08-14 19:16 ` [PATCH] hp-wmi; Limit hotkey enable funtion Kyle Evans
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=201304130331.18301@pali \
--to=pali.rohar@gmail.com \
--cc=kvans32@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--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;
as well as URLs for NNTP newsgroup(s).