From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ike Panhc <ikepanhc@gmail.com>, Hans de Goede <hansg@kernel.org>,
Rong Zhang <i@rong.moe>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, "Gergo Koteles" <soyer@irl.hu>,
"Barnabás Pőcze" <pobrn@protonmail.com>
Subject: Re: [PATCH 0/2] platform/x86: ideapad-laptop: Fix FnLock & kbd backlight not remembered among boots
Date: Tue, 08 Jul 2025 13:24:26 +0300 [thread overview]
Message-ID: <175197026643.1629.1219841831747579403.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250707163808.155876-1-i@rong.moe>
On Tue, 08 Jul 2025 00:38:05 +0800, Rong Zhang wrote:
> I had disabled ideapad-laptop for a long time until a critical bug was
> fixed[1], and I soon noticed some behavior changes after reenabling
> ideapad-laptop.
>
> The behavior changes are about FnLock and keyboard backlight. The HW/FW
> can remember their states among boots[2]. After enabling ideapad-laptop,
> I noticed that their states were always reset to off after a reboot or a
> power cycle.
>
> [...]
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/2] platform/x86: ideapad-laptop: Fix FnLock not remembered among boots
commit: 9533b789df7e8d273543a5991aec92447be043d7
[2/2] platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots
commit: e10981075adce203eac0be866389309eeb8ef11e
--
i.
prev parent reply other threads:[~2025-07-08 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 16:38 Rong Zhang
2025-07-07 16:38 ` [PATCH 1/2] platform/x86: ideapad-laptop: Fix FnLock " Rong Zhang
2025-07-07 17:23 ` Hans de Goede
2025-07-07 16:38 ` [PATCH 2/2] platform/x86: ideapad-laptop: Fix kbd backlight " Rong Zhang
2025-07-07 17:24 ` Hans de Goede
2025-07-08 10:24 ` 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=175197026643.1629.1219841831747579403.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=i@rong.moe \
--cc=ikepanhc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
--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
all inboxes | Powered by JetHome®