From: Jonathan Woithe <jwoithe@just42.net>
To: Jelle van der Waa <jvanderwaa@redhat.com>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/2] platform/x86: clamp charge thresholds on fujitsu
Date: Mon, 9 Jun 2025 20:17:53 +0930 [thread overview]
Message-ID: <aEa72cwW5ENuQX6Z@marvin.atrad.com.au> (raw)
In-Reply-To: <20250609102115.36936-1-jvanderwaa@redhat.com>
On Mon, Jun 09, 2025 at 12:21:12PM +0200, Jelle van der Waa wrote:
> For userspace programs it is not know what the valid charge control
> threshold values are, clamping them to the nearest supported threshold
> makes the API easier to use for power management daemons such as UPower.
>
> Jelle van der Waa (2):
> platform/x86: fujitsu: use unsigned int for kstrtounit
> platform/x86: fujitsu: clamp charge_control_end_threshold values to 50
>
> drivers/platform/x86/fujitsu-laptop.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> --
> 2.49.0
This patch series looks good to me.
Acked-by: Jonathan Woithe <jwoithe@just42.net>
prev parent reply other threads:[~2025-06-09 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 10:21 [PATCH 0/2] platform/x86: clamp charge thresholds on fujitsu Jelle van der Waa
2025-06-09 10:21 ` [PATCH 1/2] platform/x86: fujitsu: use unsigned int for kstrtounit Jelle van der Waa
2025-06-09 10:36 ` Hans de Goede
2025-06-13 10:14 ` Ilpo Järvinen
2025-06-09 10:21 ` [PATCH 2/2] platform/x86: fujitsu: clamp charge_control_end_threshold values to 50 Jelle van der Waa
2025-06-09 10:38 ` Hans de Goede
2025-06-09 10:47 ` Jonathan Woithe [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=aEa72cwW5ENuQX6Z@marvin.atrad.com.au \
--to=jwoithe@just42.net \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jvanderwaa@redhat.com \
--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