From: Jackie Dong <xy-jackie@139.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>, hdegoede@redhat.com
Cc: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, kuurtb@gmail.com,
W_Armin@gmx.de, dongeg1@lenovo.com,
Mark Pearson <mpearson-lenovo@squebb.ca>
Subject: Re: [PATCH v11] platform/x86:lenovo-wmi-hotkey-utilities.c:Support for mic and audio mute LEDs
Date: Tue, 4 Mar 2025 10:45:27 +0800 [thread overview]
Message-ID: <5a033664-4290-4327-8417-3148e4bc1704@139.com> (raw)
In-Reply-To: <174101234673.8641.771885577184828253.b4-ty@linux.intel.com>
On 3/3/25 22:32, Ilpo Järvinen wrote:
> On Sat, 22 Feb 2025 19:45:31 +0800, Jackie Dong wrote:
>
>> Implement Lenovo utility data WMI calls needed to make LEDs
>> work on Ideapads that support this GUID.
>> This enables the mic and audio LEDs to be updated correctly.
>>
>> Tested on below samples.
>> ThinkBook 13X Gen4 IMH
>> ThinkBook 14 G6 ABP
>> ThinkBook 16p Gen4-21J8
>> ThinkBook 16 G8 IRL
>> ThinkBook 16 G7+ ASP
>>
>> [...]
>
>
> 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/1] platform/x86:lenovo-wmi-hotkey-utilities.c: Support for mic and audio mute LEDs
> commit: 61250669eaa9fd480e0f1c3cec107924b6a06b46
>
> --
> i.
>
Hi Ilpo,
Thanks for your confirmation and help for this patch.
Best Regards,
Jackie Dong
prev parent reply other threads:[~2025-03-04 2:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 11:45 [PATCH v11] platform/x86:lenovo-wmi-hotkey-utilities.c: Support " Jackie Dong
2025-02-22 21:33 ` Armin Wolf
2025-02-28 9:00 ` [PATCH v11] platform/x86:lenovo-wmi-hotkey-utilities.c: Supportfor " Jackie Dong
2025-03-03 14:32 ` [PATCH v11] platform/x86:lenovo-wmi-hotkey-utilities.c: Support for " Ilpo Järvinen
2025-03-04 2:45 ` Jackie Dong [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=5a033664-4290-4327-8417-3148e4bc1704@139.com \
--to=xy-jackie@139.com \
--cc=W_Armin@gmx.de \
--cc=dongeg1@lenovo.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.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®