From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Nikodem Sanecki <nikodemsanecki@gmail.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Mark Pearson <mpearson-lenovo@squebb.ca>,
Abduvaliy Abdulazizov <abduvaliy.hbai@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mika Westerberg <westeri@kernel.org>,
linux-gpio@vger.kernel.org,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: ThinkPad L13 Gen 2 AMD (21AB): Caps Lock LED broken by ACPI GPIO 11 interrupt conflict
Date: Mon, 19 Oct 2026 10:39:26 +0300 [thread overview]
Message-ID: <atXJLs354lk3lFES@ashevche-desk.local> (raw)
In-Reply-To: <CAAUQFRPFkwMe4fx7xV1iDb2sAb-opYcVo=wLr-F5hwjEEU8ymw@mail.gmail.com>
On Fri, Oct 16, 2026 at 07:33:49PM +0100, Nikodem Sanecki wrote:
> I've tested your patch on my ThinkPad L13 Gen 2 AMD. The Caps Lock LED
> works without the kernel parameter, including after cold boots and
> suspend/resume. All other hardware I've tested works normally, with no
> regressions observed.
>
> Tested-by: Nikodem Sanecki nikodemsanecki@gmail.com
Wrong thread. Please reply with the same there.
> Thanks for the fix!
Thanks for testing, but please stop top-posting!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-19 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAUQFRPW-rbcZV-=qV1NMjF_358sdJTiGvQuRxRqAsehY+J9Qg@mail.gmail.com>
2026-10-15 18:25 ` Andy Shevchenko
2026-10-15 18:31 ` Andy Shevchenko
2026-10-15 18:48 ` Mario Limonciello
2026-10-15 19:24 ` Mark Pearson
2026-10-15 20:13 ` Nikodem Sanecki
2026-10-15 20:26 ` Mario Limonciello
[not found] ` <CAAUQFRO49_T8iRdL3zYaj82Y_rgPTgM6VjScN3rqK89NmRzLqg@mail.gmail.com>
2026-10-16 18:33 ` Nikodem Sanecki
2026-10-19 7:39 ` Andy Shevchenko [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=atXJLs354lk3lFES@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=abduvaliy.hbai@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=nikodemsanecki@gmail.com \
--cc=westeri@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®