linux-kernel - Re: [PATCH] HID: asus: Fix keyboard support

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] [day] [month] [year] [list]

Date:   Mon, 19 Dec 2016 11:26:31 +0100 (CET)
From:   Jiri Kosina <jikos@...nel.org>
To:     Benjamin Tissoires <benjamin.tissoires@...hat.com>
cc:     Brendan McGrath <redmcg@...mandi.dyndns.org>,
        Henrik Rydberg <rydberg@...math.org>,
        linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
        Victor Vlasenko <victor.vlasenko@...gears.com>
Subject: Re: [PATCH] HID: asus: Fix keyboard support

On Sat, 10 Dec 2016, Benjamin Tissoires wrote:

> Sorry for breaking the existing device.
> 
> I have a few minor issues with your patch, but I'll let Jiri says
> whether or not you need a v2.
> 
> On Dec 10 2016 or thereabouts, Brendan McGrath wrote:
> > The previous submission which added Touchpad support broke the
> > Keyboard support of this driver. This patch:
> > 1. fixes the Keyboard support (by assigning drvdata->input);
> 
> This is actually what was breaking your keyboard (plus item 4 which is
> cosmetic). Ideally, this should be in a separate patch.
> 
> > 2. renames NOTEBOOK_QUIRKS to KEYBOARD_QUIRKS;
> > 3. adds the NO_INIT_REPORT quirk to the KEYBOARD_QUIRKS; and
> 
> Points 2 and 3 are actually improvements because I can't seem to find
> that previously the keyboard had this quirk. I understand it is
> valuable, but it should be in a different patch IMO.
> 
> > 4. sets the input->name to 'Asus Keyboard' for the keyboard 
> 
> Cosmetic, but so important :)
> 
> Anyway, the patch in its current form is:
> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@...hat.com>
> 
> But it might be good to split it in 2 (it will depend on Jiri I guess).

Having it separate would be slightly better next time, but I don't 
consider that really to be a show stopper. Queuing in 
for-4.10/upstream-fixes, thanks.

-- 
Jiri Kosina
SUSE Labs