From: Aaron Erhardt <aer@tuxedocomputers.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: wse@tuxedocomputers.com, Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v3 4/6] platform/x86/tuxedo: Fix keyboard LED map ordering
Date: Tue, 15 Sep 2026 15:55:33 +0200 [thread overview]
Message-ID: <dfa01359-e2b3-4e02-85d2-220e48b85594@tuxedocomputers.com> (raw)
In-Reply-To: <35453b67-df97-a5a6-99a1-9746500796e9@linux.intel.com>
Am 15.09.26 um 15:00 schrieb Ilpo Järvinen:
> On Wed, 26 Aug 2026, Aaron Erhardt wrote:
>
>> The LED mappings in sirius_16_[iso|ansii]_kbl_map did contain a
>> flipped line that caused LEDs to turn on in the wrong order when
>> counting up the Lamp ID.
>>
>> Cc: stable@vger.kernel.org
>
> And the Fixes tag?
I assume this is mainly for the stable maintainers to be able to track down
when the bug was introduced, right? I thought "Fixes:" would only be used for
regression bugs.
The only commit relevant to this is the one that introduced the driver itself:
cfd84b3f419bf0aec60ecddc92c61b539c339ec9
I correct this in the next series.
>
>> Signed-off-by: Aaron Erhardt <aer@tuxedocomputers.com>
>> ---
>> drivers/platform/x86/tuxedo/nb04/wmi_ab.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/platform/x86/tuxedo/nb04/wmi_ab.c b/drivers/platform/x86/tuxedo/nb04/wmi_ab.c
>> index 8f1ffca0430d..2b985b030197 100644
>> --- a/drivers/platform/x86/tuxedo/nb04/wmi_ab.c
>> +++ b/drivers/platform/x86/tuxedo/nb04/wmi_ab.c
>> @@ -232,8 +232,8 @@ static const struct tux_kbl_map_entry_t sirius_16_ansii_kbl_map[] = {
>> { 0x2e, { 246000, 67500, 5250 } },
>> { 0x2a, { 269500, 67500, 5250 } },
>> { 0x53, { 294500, 67500, 5250 } },
>> - { 0x55, { 311200, 67500, 5250 } },
>> - { 0x54, { 327900, 67500, 5250 } },
>> + { 0x54, { 311200, 67500, 5250 } },
>> + { 0x55, { 327900, 67500, 5250 } },
>> { 0x56, { 344600, 67500, 5250 } },
>> { 0x2b, { 31000, 85500, 5500 } },
>> { 0x14, { 51500, 85500, 5500 } },
>> @@ -337,8 +337,8 @@ static const struct tux_kbl_map_entry_t sirius_16_iso_kbl_map[] = {
>> { 0x2e, { 246000, 67500, 5250 } },
>> { 0x2a, { 269500, 67500, 5250 } },
>> { 0x53, { 294500, 67500, 5250 } },
>> - { 0x55, { 311200, 67500, 5250 } },
>> - { 0x54, { 327900, 67500, 5250 } },
>> + { 0x54, { 311200, 67500, 5250 } },
>> + { 0x55, { 327900, 67500, 5250 } },
>> { 0x56, { 344600, 67500, 5250 } },
>> { 0x2b, { 31000, 85500, 5500 } },
>> { 0x14, { 51500, 85500, 5500 } },
>>
>
next prev parent reply other threads:[~2026-09-15 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 8:11 [PATCH v3 0/6] platform/x86/tuxedo: Fixes for TUXEDO NB04 driver Aaron Erhardt
2026-08-26 8:11 ` [PATCH v3 1/6] platform/x86/tuxedo: Don't use device driver data Aaron Erhardt
2026-08-26 8:27 ` Werner Sembach
2026-08-26 8:11 ` [PATCH v3 2/6] platform/x86/tuxedo: Set HID report ID on success Aaron Erhardt
2026-08-26 8:27 ` Werner Sembach
2026-08-26 8:11 ` [PATCH v3 3/6] platform/x86/tuxedo: Use intensity according to HID spec Aaron Erhardt
2026-08-26 8:27 ` Werner Sembach
2026-08-26 8:11 ` [PATCH v3 4/6] platform/x86/tuxedo: Fix keyboard LED map ordering Aaron Erhardt
2026-08-26 8:28 ` Werner Sembach
2026-09-15 13:00 ` Ilpo Järvinen
2026-09-15 13:55 ` Aaron Erhardt [this message]
2026-08-26 8:11 ` [PATCH v3 5/6] platform/x86/tuxedo: Update and extend documentation Aaron Erhardt
2026-08-26 8:28 ` Werner Sembach
2026-09-15 13:08 ` Ilpo Järvinen
2026-09-15 14:07 ` Aaron Erhardt
2026-08-26 8:11 ` [PATCH v3 6/6] MAINTAINERS: Add Aaron Erhardt as maintainer of TUXEDO DRIVERS Aaron Erhardt
2026-08-26 8:28 ` Werner Sembach
2026-09-03 11:27 ` [PATCH v3 0/6] platform/x86/tuxedo: Fixes for TUXEDO NB04 driver Aaron Erhardt
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=dfa01359-e2b3-4e02-85d2-220e48b85594@tuxedocomputers.com \
--to=aer@tuxedocomputers.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=wse@tuxedocomputers.com \
/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®