From: Hans de Goede <hdegoede@redhat.com>
To: "Gergo Koteles" <soyer@irl.hu>,
"Ike Panhc" <ike.pan@canonical.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 0/3] add FnLock LED class device to ideapad laptops
Date: Mon, 15 Apr 2024 15:35:33 +0200 [thread overview]
Message-ID: <b8236348-476d-4c50-88ab-0409e4bf6bf0@redhat.com> (raw)
In-Reply-To: <cover.1712063200.git.soyer@irl.hu>
Hi,
On 4/2/24 3:20 PM, Gergo Koteles wrote:
> Hi All,
>
> This patch series adds a new LED_FUNCTION_FNLOCK define as "fnlock" and
> adds a new FnLock LED class device into the ideapad-laptop driver.
>
> This helps to display FnLock LED status in OSD or other places.
Thank you for your patch-series, I've applied the series to my
review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
>
> Best regards,
> Gergo
>
> Gergo Koteles (3):
> dt-bindings: leds: add LED_FUNCTION_FNLOCK
> platform/x86: ideapad-laptop: add fn_lock_get/set functions
> platform/x86: ideapad-laptop: add FnLock LED class device
>
> drivers/platform/x86/ideapad-laptop.c | 133 +++++++++++++++++++++++---
> include/dt-bindings/leds/common.h | 1 +
> 2 files changed, 123 insertions(+), 11 deletions(-)
>
>
> base-commit: 39cd87c4eb2b893354f3b850f916353f2658ae6f
prev parent reply other threads:[~2024-04-15 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 13:20 [PATCH 0/3] add FnLock LED class device to ideapad laptops Gergo Koteles
2024-04-02 13:21 ` [PATCH 1/3] dt-bindings: leds: add LED_FUNCTION_FNLOCK Gergo Koteles
2024-04-02 13:55 ` Krzysztof Kozlowski
2024-04-02 14:36 ` Gergo Koteles
2024-04-02 18:08 ` Krzysztof Kozlowski
2024-04-02 18:50 ` Gergo Koteles
2024-04-03 8:33 ` Hans de Goede
2024-04-03 8:31 ` Hans de Goede
2024-04-03 8:36 ` Krzysztof Kozlowski
2024-04-03 8:39 ` Hans de Goede
2024-04-03 8:46 ` Krzysztof Kozlowski
2024-04-03 8:51 ` Hans de Goede
2024-04-11 7:13 ` Lee Jones
2024-04-02 13:21 ` [PATCH 2/3] platform/x86: ideapad-laptop: add fn_lock_get/set functions Gergo Koteles
2024-04-08 15:49 ` Hans de Goede
2024-04-08 15:49 ` Hans de Goede
2024-04-02 13:21 ` [PATCH 3/3] platform/x86: ideapad-laptop: add FnLock LED class device Gergo Koteles
2024-04-08 15:50 ` Hans de Goede
2024-04-15 13:35 ` Hans de Goede [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=b8236348-476d-4c50-88ab-0409e4bf6bf0@redhat.com \
--to=hdegoede@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ike.pan@canonical.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@kernel.org \
--cc=soyer@irl.hu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).