From: "João Paulo Rechi Vita" <jprvita@gmail.com>
To: Darren Hart <dvhart@infradead.org>
Cc: platform-driver-x86@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux@endlessm.com,
"João Paulo Rechi Vita" <jprvita@endlessm.com>
Subject: [PATCH 0/1] asus-wireless: Use the correct HSWC parameter for each HID
Date: Thu, 26 Jan 2017 10:00:30 -0500 [thread overview]
Message-ID: <20170126150031.11840-1-jprvita@endlessm.com> (raw)
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
next reply other threads:[~2017-01-26 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 15:00 João Paulo Rechi Vita [this message]
2017-01-26 15:00 ` [PATCH 1/1] " João Paulo Rechi Vita
2017-01-27 15:26 ` Andy Shevchenko
2017-02-01 12:20 ` João Paulo Rechi Vita
2017-02-04 15:02 ` Andy Shevchenko
2017-02-07 21:44 ` João Paulo Rechi Vita
2017-02-07 21:45 ` [PATCHv2] platform/x86: asus-wireless: Use per-HID HSWC parameters João Paulo Rechi Vita
2017-02-13 22:09 ` Andy Shevchenko
2017-02-07 23:37 ` [PATCH 1/1] asus-wireless: Use the correct HSWC parameter for each HID Andy Shevchenko
2017-02-08 17:04 ` João Paulo Rechi Vita
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=20170126150031.11840-1-jprvita@endlessm.com \
--to=jprvita@gmail.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=dvhart@infradead.org \
--cc=jprvita@endlessm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--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
all inboxes | Powered by JetHome®