From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH 1/5] atkbd: Fix key release for Fn keys on Samsung series 5 ultra 540UC
Date: Mon, 29 Jul 2013 07:04:32 -0300 [thread overview]
Message-ID: <20130729070432.726becc3@samsung.com> (raw)
In-Reply-To: <20130729044909.GA8539@core.coreip.homeip.net>
Em Sun, 28 Jul 2013 21:49:09 -0700
Dmitry Torokhov <dmitry.torokhov@gmail.com> escreveu:
> Hi Mauro,
>
>
> On Mon, Jul 29, 2013 at 12:59:35AM -0300, Mauro Carvalho Chehab wrote:
> > Samsung series 5 ultra notebooks don't produce release events for certain
> > keys (Fn+F1, Fn+F11, Fn+F12 and Fn Lock). Add those keys at the release
> > fixup table.
> >
>
> As I mentioned, the force release should be handled by udev instead of
> adding kernel driver quirk.
Ah, OK. I'll drop both patches 1 and 2 on a next patchset.
--
Cheers,
Mauro
prev parent reply other threads:[~2013-07-29 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 3:59 [PATCH 1/5] atkbd: Fix key release for Fn keys on Samsung series 5 ultra 540UC Mauro Carvalho Chehab
2013-07-29 3:59 ` [PATCH 2/5] atkbd: Fix key release for Fn keys on Samsung series 5 550P5C Mauro Carvalho Chehab
2013-07-29 4:49 ` Dmitry Torokhov
2013-07-29 3:59 ` [PATCH 3/5] input.h: add keycodes for Fn Lock Mauro Carvalho Chehab
2013-07-29 4:53 ` Dmitry Torokhov
2013-07-29 10:03 ` Mauro Carvalho Chehab
2013-07-29 10:50 ` Mauro Carvalho Chehab
2013-07-30 7:14 ` Dmitry Torokhov
2013-07-30 9:56 ` Mauro Carvalho Chehab
2013-07-29 3:59 ` [PATCH 4/5] atkbd: add support for handling KEY_FNLOCK Mauro Carvalho Chehab
2013-07-29 3:59 ` [PATCH 5/5] atkbd: only enable SW_FNLOCK on keyboards that have FN LOCK key Mauro Carvalho Chehab
2013-07-29 4:49 ` [PATCH 1/5] atkbd: Fix key release for Fn keys on Samsung series 5 ultra 540UC Dmitry Torokhov
2013-07-29 10:04 ` Mauro Carvalho Chehab [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=20130729070432.726becc3@samsung.com \
--to=m.chehab@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@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).