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 v3 0/3] toshiba_acpi: Hotkeys and event handling changes
Date: Wed, 3 Dec 2014 05:38:33 -0800 [thread overview]
Message-ID: <20141203133833.GH75099@vmdeb7> (raw)
In-Reply-To: <1417749767-3898-1-git-send-email-coproscefalo@gmail.com>
On Thu, Dec 04, 2014 at 08:22:44PM -0700, Azael Avalos wrote:
> These patches change the current code to accomodate the handling
> of more events, since so far, it only handles hotkey events (0x80),
> move the hotkey enabling code to a sub function to avoid duplication,
> and add event 0x92 which indicates a change in the keyboard backlight
> mode.
>
> Changes since V3:
> - Removed a left over variable from the split in patch 02 and
> moved it to patch 03 (where it belongs)
> - A bit more verbose description on patch 03
>
> Azael Avalos (3):
> toshiba_acpi: Move hotkey enabling code to own function
> toshiba_acpi: Change notify funtion to handle more events
> toshiba_acpi: Add keyboard backlight mode change event
Queued. Your 1/3 commit message reverted to the short line length, might want to
update your tools. ;-) I took care of it.
Thanks Azael,
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2014-12-05 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 3:22 [PATCH v3 0/3] toshiba_acpi: Hotkeys and event handling changes Azael Avalos
2014-12-03 13:38 ` Darren Hart [this message]
2014-12-05 3:22 ` [PATCH v3 1/3] toshiba_acpi: Move hotkey enabling code to own function Azael Avalos
2014-12-05 3:22 ` [PATCH v3 2/3] toshiba_acpi: Change notify funtion to handle more events Azael Avalos
2014-12-05 3:22 ` [PATCH v3 3/3] toshiba_acpi: Add keyboard backlight mode change event 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=20141203133833.GH75099@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