From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ike Panhc <ikepanhc@gmail.com>,
Mark Pearson <mpearson-lenovo@squebb.ca>,
"Derek J. Clark" <derekjohn.clark@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, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] platform/x86: ideapad-laptop: Fix unexpected charge_types on probe
Date: Thu, 19 Nov 2026 16:42:32 +0200 [thread overview]
Message-ID: <179509935205.9442.4946497290520941124.b4-ty@b4> (raw)
In-Reply-To: <20261018-ideapad-fix-charge-types-v1-0-db52e3bb061a@rong.moe>
On Sun, 18 Oct 2026 07:16:17 +0800, Rong Zhang wrote:
> It was reported [1] that some unfortunate combinations of BIOS and
> Lenovo utilities (e.g., Legion Go 2 + Legion Space) may enable Rapid
> Charge and Conservation Mode at the same time, which is very out of
> sepc.
>
> If both are enabled during a previous Windows boot, ideapad-laptop will
> see both bits set and correctly shout "unexpected charge_types".
>
> [...]
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.
FYI [if applicable to your patch], as per Linus' policy change, also
fixes are mostly routed through for-next unless the fix is for a
commit introduced in the most recent cycle or is clearly a regression
fix.
The list of commits applied:
[1/2] platform/x86: ideapad-laptop: Factor out charge_types methods for internal use
commit: 45e6d68a4cf9d9b5b15ce94062f1aba1078b47ed
[2/2] platform/x86: ideapad-laptop: Fix unexpected charge_types on probe
commit: 721027ef36056f38eb690a17f00be134bd9f9e75
--
i.
prev parent reply other threads:[~2026-11-19 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 23:16 Rong Zhang
2026-10-17 23:16 ` [PATCH 1/2] platform/x86: ideapad-laptop: Factor out charge_types methods for internal use Rong Zhang
2026-10-17 23:16 ` [PATCH 2/2] platform/x86: ideapad-laptop: Fix unexpected charge_types on probe Rong Zhang
2026-10-18 5:30 ` [PATCH 0/2] " Derek J. Clark
2026-10-18 14:19 ` Rong Zhang
2026-10-19 1:17 ` Derek J. Clark
2026-11-19 15:32 ` Rong Zhang
2026-11-19 14:42 ` 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=179509935205.9442.4946497290520941124.b4-ty@b4 \
--to=ilpo.jarvinen@linux.intel.com \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=i@rong.moe \
--cc=ikepanhc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@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®