linux-kernel - Re: [PATCH 0/3] toshiba_acpi: Hotkey handling and keymap updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150306183450.GK19001@vmdeb7>
Date:	Fri, 6 Mar 2015 10:34:50 -0800
From:	Darren Hart <dvhart@...radead.org>
To:	Azael Avalos <coproscefalo@...il.com>
Cc:	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] toshiba_acpi: Hotkey handling and keymap updates

On Thu, Feb 26, 2015 at 10:57:11AM -0700, Azael Avalos wrote:
> These patches add support to a new function that queries the supported Hotkey
> Event Type, making the use of the DMI matching unnecessary and also fixes
> the "Special Functions" mode on some laptops.
> 
> Azael Avalos (3):
>   toshiba_acpi: Add Hotkey Event Type function and definitions
>   toshiba_acpi: Use the Hotkey Event Type function for keymap choosing
>   toshiba_acpi: Fix the enabling of the Special Functions
> 
>  drivers/platform/x86/toshiba_acpi.c | 97 ++++++++++++++++++++++++-------------
>  1 file changed, 64 insertions(+), 33 deletions(-)
> 

Would you also include a MAINTAINERS update, adding yourself as the
thoshiba-acpi and possibly the toshiba-haps drivers? This helps ensure you get
Cc'd. I'll also look for you to pre-screen any other submission to these drivers
and provide your Reviewed-by before I merge them.

-- 
Darren Hart
Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/