All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Hung <alex.hung@canonical.com>
To: Jonathan Nieder <jrnieder@gmail.com>,
	corentincj@iksaif.net, mjg@redhat.com,
	acpi4asus-user@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] asus-wmi: use ASUS_WMI_METHODID_DSTS2 as default DSTS ID.
Date: Wed, 27 Jun 2012 15:53:32 +0800	[thread overview]
Message-ID: <4FEABBFC.6090708@canonical.com> (raw)
In-Reply-To: <20120626215806.GM21479@carsten-otto>

On 06/27/2012 05:58 AM, Carsten Otto wrote:
> Dear all,
>
> On Tue, Jun 26, 2012 at 04:39:58PM -0500, Jonathan Nieder wrote:
>> After applying the patch described above to 3.2.21, multimedia keys
>> work.
>
> To be precise, only some of the Fn keys work. I will update the
> bug report at http://bugs.debian.org/679158 now. Please contact me if
> you need further information,
>
> Best regards,

Some Fn keys fail to work is probably the result of un-handled events, 
i.e. asus_wmi: Unknown key 7a pressed.

Do you always receive the error messages for each of the Fn-keys that 
fails? I can take a closer look and try to fix each of them. I don't 
have a Asus Zenbook Prime but I can check on other available Asus machines.

Best Regards,
Alex Hung

  reply	other threads:[~2012-06-27  7:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  3:47 [PATCH] asus-wmi: use ASUS_WMI_METHODID_DSTS2 as default DSTS ID Alex Hung
2012-06-20  3:50 ` Alex Hung
2012-06-26 21:39 ` Jonathan Nieder
2012-06-26 21:58   ` Carsten Otto
2012-06-27  7:53     ` Alex Hung [this message]
2012-06-27 22:17       ` Jonathan Nieder
2012-06-28  8:18         ` Carsten Otto
2012-09-18 10:21         ` Carsten Otto
2012-09-18 20:54           ` Corentin Chary
2012-06-29 12:21 ` Corentin Chary

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=4FEABBFC.6090708@canonical.com \
    --to=alex.hung@canonical.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentincj@iksaif.net \
    --cc=jrnieder@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.