From: Hans de Goede <hdegoede@redhat.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 0/1] thinkpad_acpi: Add mappings for F9 - F12 hotkeys on X240 / T440 / T540
Date: Thu, 10 Apr 2014 10:17:02 +0200 [thread overview]
Message-ID: <5346537E.6010201@redhat.com> (raw)
In-Reply-To: <20140410001221.GA23977@khazad-dum.debian.net>
Hi,
On 04/10/2014 02:12 AM, Henrique de Moraes Holschuh wrote:
> On Wed, 09 Apr 2014, Matthew Garrett wrote:
>> On Wed, Apr 09, 2014 at 03:03:01PM -0300, Henrique de Moraes Holschuh wrote:
>>> On Wed, 09 Apr 2014, Hans de Goede wrote:
>>>> This patch seems to have fallen through the cracks, so here is a resend.
>>>
>>> Sort of. There was a doubt about one of the keycodes.
>>
>> I think I'm ok with the keycode.
>
> Ok. Now, provided that it doesn't clash with the other thinkpads (in which
> case we'd just add selective keymaps), we can merge.
It does not clash with the new Carbon X1 2nd generation stuff, see:
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/platform/x86/thinkpad_acpi.c?id=8f5f86abc6593b6d600712435e2f24a7a098b951
Basically the new stuff uses hotkey codes >= TPACPI_HOTKEY_MAP_LEN,
where as my patch adds mappings for codes < TPACPI_HOTKEY_MAP_LEN.
(Where TPACPI_HOTKEY_MAP_LEN == 32)
> Heck, we can fix that later too, it doesn't count as an ABI break, these
> keymaps are _already_ configurable from userspace _and_ usually reconfigured
> by userspace, the driver just tries to provide sane defaults. So...
>
> Acked-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Thanks & Regards,
Hans
prev parent reply other threads:[~2014-04-10 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 9:46 [PATCH v2 0/1] thinkpad_acpi: Add mappings for F9 - F12 hotkeys on X240 / T440 / T540 Hans de Goede
2014-04-09 9:46 ` [PATCH v2] " Hans de Goede
2014-04-09 18:03 ` [PATCH v2 0/1] " Henrique de Moraes Holschuh
2014-04-09 18:27 ` Matthew Garrett
2014-04-10 0:12 ` Henrique de Moraes Holschuh
2014-04-10 8:17 ` Hans de Goede [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=5346537E.6010201@redhat.com \
--to=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--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