From: Aaron Erhardt <aer@tuxedocomputers.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Werner Sembach <wse@tuxedocomputers.com>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/6] platform/x86/tuxedo: Fix keyboard LED map ordering
Date: Tue, 6 Oct 2026 09:41:35 +0200 [thread overview]
Message-ID: <c76f4274-bcf6-4a56-908d-10e08405f5ea@tuxedocomputers.com> (raw)
In-Reply-To: <c6592aba-a3af-f012-361f-52e29b070459@linux.intel.com>
Am 05.10.26 um 16:06 schrieb Ilpo Järvinen:
> On Mon, 28 Sep 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.
>>
>> Fixes: cfd84b3f419b
>
> Please see Documentation/process/submitting-patches.rst how to format
> the Fixes tag properly.
>
> You seem to also have not carried over Werner's Reviewed-by tags to a new
> version. Whenever you're submitting a new version of the series, collect
> the tags given to the previous version. (Only if you've done very major
> changes to the patches, it may be warranted to not include tags given
> earlier.)
>
> Generally, maintainer tools will only pick tags for the current version of
> the series (err'ing to the side of caution) which is why submitters are
> expected to do that when a new version gets posted.
>
I read that exact document, but only the lower section about when and not how.
Sorry for that. I'll fix both problems in the next series.
>> 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 } },
>>
>
next prev parent reply other threads:[~2026-10-06 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 8:36 [PATCH v4 0/6] platform/x86/tuxedo: Fixes for TUXEDO NB04 driver Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 1/6] platform/x86/tuxedo: Don't use device driver data Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 2/6] platform/x86/tuxedo: Set HID report ID on success Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 3/6] platform/x86/tuxedo: Use intensity according to HID spec Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 4/6] platform/x86/tuxedo: Fix keyboard LED map ordering Aaron Erhardt
2026-10-05 14:06 ` Ilpo Järvinen
2026-10-06 7:41 ` Aaron Erhardt [this message]
2026-09-28 8:36 ` [PATCH v4 5/6] platform/x86/tuxedo: Update and extend documentation Aaron Erhardt
2026-09-28 8:36 ` [PATCH v4 6/6] MAINTAINERS: Add Aaron Erhardt as maintainer of TUXEDO DRIVERS 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=c76f4274-bcf6-4a56-908d-10e08405f5ea@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®