linux-kernel - [PATCH 0/1] asus-wireless: Use the correct HSWC parameter for each HID

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

Message-Id: <20170126150031.11840-1-jprvita@endlessm.com>
Date:   Thu, 26 Jan 2017 10:00:30 -0500
From:   "João Paulo Rechi Vita" <jprvita@...il.com>
To:     Darren Hart <dvhart@...radead.org>
Cc:     platform-driver-x86@...r.kernel.org,
        acpi4asus-user@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
        linux@...lessm.com,
        João Paulo Rechi Vita <jprvita@...lessm.com>
Subject: [PATCH 0/1] asus-wireless: Use the correct HSWC parameter for each HID

As stated in the commit message, different machines can use different values to
represent LED ON/OFF, and this commit makes sure we use the correct value pair
for each _HID.

I don't know if there is a better way to store these pairs than in a structure
matching the device_ids[] indexing that would avoid looping through
device_ids[] in asus_wireless_add(). I'm happy to try suggestions to improve
that.

João Paulo Rechi Vita (1):
  asus-wireless: Use the correct HSWC parameter for each HID

 drivers/platform/x86/asus-wireless.c | 46 ++++++++++++++++++++++++++----------
 1 file changed, 33 insertions(+), 13 deletions(-)

-- 
2.11.0