From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hansg@kernel.org, chumuzero@gmail.com, corbet@lwn.net,
cs@tuxedo.de, wse@tuxedocomputers.com, ggo@tuxedocomputers.com,
Armin Wolf <W_Armin@gmx.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, rdunlap@infradead.org,
alok.a.tiwari@oracle.com, linux-leds@vger.kernel.org,
lee@kernel.org, pobrn@protonmail.com, nathan@kernel.org
Subject: Re: [PATCH v6 0/2] Add support for Uniwill laptop features
Date: Mon, 10 Nov 2025 14:00:40 +0200 [thread overview]
Message-ID: <176277604087.8442.15648008989886648183.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20251102172942.17879-1-W_Armin@gmx.de>
On Sun, 02 Nov 2025 18:29:40 +0100, Armin Wolf wrote:
> This patch series adds support for the various features found on
> laptops manufactured by Uniwill. Those features are:
>
> - battery charge limiting
> - RGB lightbar control
> - hwmon support
> - improved hotkey support
> - keyboard-related settings
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/2] platform/x86: Add Uniwill laptop driver
commit: d050479693bb91da5a0e305ca9dd59f4c0b55dd3
[2/2] Documentation: laptops: Add documentation for uniwill laptops
commit: cec551ec79c2f287d1eb048f70fe4bff66cc7d41
--
i.
prev parent reply other threads:[~2025-11-10 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 17:29 Armin Wolf
2025-11-02 17:29 ` [PATCH v6 1/2] platform/x86: Add Uniwill laptop driver Armin Wolf
2025-11-05 14:24 ` Ilpo Järvinen
2025-11-05 22:02 ` Armin Wolf
2025-11-02 17:29 ` [PATCH v6 2/2] Documentation: laptops: Add documentation for uniwill laptops Armin Wolf
2025-11-10 12:00 ` 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=176277604087.8442.15648008989886648183.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=alok.a.tiwari@oracle.com \
--cc=chumuzero@gmail.com \
--cc=corbet@lwn.net \
--cc=cs@tuxedo.de \
--cc=ggo@tuxedocomputers.com \
--cc=hansg@kernel.org \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
--cc=rdunlap@infradead.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®