From: Aaron Erhardt <aer@tuxedocomputers.com>
To: wse@tuxedocomputers.com, hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 4/6] platform/x86/tuxedo: Fix keyboard LED map ordering
Date: Tue, 28 Jul 2026 16:46:53 +0200 [thread overview]
Message-ID: <cd0f5c3a-73b9-4954-94b3-27818b4c9664@tuxedocomputers.com> (raw)
In-Reply-To: <20260728115938.125444-1-aer@tuxedocomputers.com>
This patch was sent directly to stable by accident, separate from the rest of the patch series.
Please ignore it. It will come with v2 or a later revisions of the series through master.
Sorry for the inconvenience.
Best regards
Aaron
Am 28.07.26 um 13:59 schrieb Aaron Erhardt:
> 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
> 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 } },
prev parent reply other threads:[~2026-07-28 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 11:59 Aaron Erhardt
2026-07-28 14:46 ` Aaron Erhardt [this message]
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=cd0f5c3a-73b9-4954-94b3-27818b4c9664@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=stable@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®