public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] toshiba_acpi: Use the Hotkey Event Type function for keymap choosing
Date: Fri, 6 Mar 2015 10:22:48 -0800	[thread overview]
Message-ID: <20150306182248.GH19001@vmdeb7> (raw)
In-Reply-To: <1424973434-3032-3-git-send-email-coproscefalo@gmail.com>

On Thu, Feb 26, 2015 at 10:57:13AM -0700, Azael Avalos wrote:
> With the previous patch adding support to "Hotkey Event Type", we can
> now use the type to distinguish which keymap to use.
> 
> This patch changes the toshiba_acpi_setup_keyboard function to make
> use of the hotkey event type to choose the correct keymap without the
> need to use the DMI matching list.

Yay!

Pending discussion on 1/3.

-- 
Darren Hart
Intel Open Source Technology Center

  reply	other threads:[~2015-03-06 18:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 17:57 [PATCH 0/3] toshiba_acpi: Hotkey handling and keymap updates Azael Avalos
2015-02-26 17:57 ` [PATCH 1/3] toshiba_acpi: Add Hotkey Event Type function and definitions Azael Avalos
2015-03-06 18:21   ` Darren Hart
2015-03-06 18:42     ` Azael Avalos
2015-03-19  3:56       ` Darren Hart
2015-02-26 17:57 ` [PATCH 2/3] toshiba_acpi: Use the Hotkey Event Type function for keymap choosing Azael Avalos
2015-03-06 18:22   ` Darren Hart [this message]
2015-02-26 17:57 ` [PATCH 3/3] toshiba_acpi: Fix the enabling of the Special Functions Azael Avalos
2015-03-06 18:28   ` Darren Hart
2015-03-06 18:52     ` Azael Avalos
2015-03-19  3:58       ` Darren Hart
2015-03-06 18:34 ` [PATCH 0/3] toshiba_acpi: Hotkey handling and keymap updates Darren Hart
2015-03-06 18:58   ` Azael Avalos

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=20150306182248.GH19001@vmdeb7 \
    --to=dvhart@infradead.org \
    --cc=coproscefalo@gmail.com \
    --cc=linux-kernel@vger.kernel.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