From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hansg@kernel.org, Armin Wolf <W_Armin@gmx.de>
Cc: wse@tuxedocomputers.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] uniwill-laptop: Input-related improvements
Date: Mon, 23 Feb 2026 18:35:17 +0200 [thread overview]
Message-ID: <177186451796.17917.11303084523071214041.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260218005101.73680-1-W_Armin@gmx.de>
On Wed, 18 Feb 2026 01:50:57 +0100, Armin Wolf wrote:
> This patch series contains a set of input-related improvements
> for the uniwill-laptop driver. The first patch renames the
> "fn_lock_toggle_enable" and "super_key_toggle_enable" sysfs attributes
> after it was discovered that the underlying hardware works differently
> than previously thought. This technically breaks user space
> applications using those sysfs attributes, but AFAIK no such users
> currently exist.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/4] platform/x86: uniwill-laptop: Rename FN lock and super key lock attrs
commit: 2d53dfacf067968a9ff90c03700fb9b28049f4c6
[2/4] platform/x86: uniwill-laptop: Fix crash on unexpected battery event
commit: 67e7eb4c130a74c5da9ab43316e00ed3186d1811
[3/4] platform/x86: uniwill-laptop: Mark FN lock status as being volatile
commit: 2be519d94544e226636c185e28ec1a72d01aab87
[4/4] platform/x86: uniwill-laptop: Handle FN lock event
commit: 9836feedcf559449e82eb0f741084086780104e5
--
i.
prev parent reply other threads:[~2026-02-23 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 0:50 Armin Wolf
2026-02-18 0:50 ` [PATCH v4 1/4] platform/x86: uniwill-laptop: Rename FN lock and super key lock attrs Armin Wolf
2026-02-18 0:50 ` [PATCH v4 2/4] platform/x86: uniwill-laptop: Fix crash on unexpected battery event Armin Wolf
2026-02-18 0:51 ` [PATCH v4 3/4] platform/x86: uniwill-laptop: Mark FN lock status as being volatile Armin Wolf
2026-02-18 0:51 ` [PATCH v4 4/4] platform/x86: uniwill-laptop: Handle FN lock event Armin Wolf
2026-02-23 16:35 ` Ilpo Järvinen [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=177186451796.17917.11303084523071214041.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hansg@kernel.org \
--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®