From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-kernel@vger.kernel.org, Denis Benato <denis.benato@linux.dev>
Cc: platform-driver-x86@vger.kernel.org,
Hans de Goede <hansg@kernel.org>,
"Luke D . Jones" <luke@ljones.dev>,
Derek John Clark <derekjohn.clark@gmail.com>,
Denis Benato <benato.denis96@gmail.com>,
Antheas Kapenekakis <lkml@antheas.dev>
Subject: Re: [PATCH] platform/x86: asus-wmi: do not enforce a battery charge threshold
Date: Tue, 24 Mar 2026 19:31:00 +0200 [thread overview]
Message-ID: <177437346005.18408.16065385347677111324.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260304132608.33815-1-denis.benato@linux.dev>
On Wed, 04 Mar 2026 14:26:08 +0100, Denis Benato wrote:
> Users are complaining for the battery limit being reset at 100% during
> the boot process while the general consensus appears to not apply
> unsolecited hardware changes, therefore stop resetting the battery
> charge limit at boot and return -ENODATA on charge_end_threshold to
> signal for an unknown limit.
>
>
> [...]
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: asus-wmi: do not enforce a battery charge threshold
commit: 186bf9031666602d61b40832181b6b6fdc3ba4dc
--
i.
prev parent reply other threads:[~2026-03-24 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 13:26 Denis Benato
2026-03-04 13:30 ` Antheas Kapenekakis
2026-03-04 13:36 ` Denis Benato
2026-03-04 13:39 ` Antheas Kapenekakis
2026-03-04 13:40 ` Antheas Kapenekakis
2026-03-04 13:51 ` Denis Benato
2026-03-04 16:07 ` Antheas Kapenekakis
2026-03-04 16:12 ` Denis Benato
2026-03-18 14:16 ` Denis Benato
2026-03-18 14:17 ` Antheas Kapenekakis
2026-03-04 13:32 ` Ilpo Järvinen
2026-03-18 14:30 ` Derek J. Clark
2026-03-24 17:31 ` 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=177437346005.18408.16065385347677111324.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=benato.denis96@gmail.com \
--cc=denis.benato@linux.dev \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=luke@ljones.dev \
--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®