From: Guenter Roeck <linux@roeck-us.net>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Benson Leung <bleung@chromium.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Guenter Roeck <groeck@chromium.org>,
chrome-platform@lists.linux.dev, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] hwmon: (cros_ec) Split out cros_ec_hwmon_get_thermal_config()
Date: Tue, 9 Jun 2026 13:52:18 -0700 [thread overview]
Message-ID: <2839056c-0827-42ed-9475-e84bed8d18a5@roeck-us.net> (raw)
In-Reply-To: <20260529-cros_ec-hwmon-fan-curve-v1-3-da6792b3830f@weissschuh.net>
On Fri, May 29, 2026 at 10:31:54PM +0200, Thomas Weißschuh wrote:
> Some upcoming changes require access to the raw
> 'struct ec_thermal_config'.
>
> Split out the logic to get it from the EC into a new helper.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Applied.
Thanks,
Guenter
next prev parent reply other threads:[~2026-06-09 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 20:31 [PATCH 0/5] hwmon: (cros_ec) Add support for fan curves Thomas Weißschuh
2026-05-29 20:31 ` [PATCH 1/5] hwmon: (cros_ec) Implement custom kelvin to celsius conversions Thomas Weißschuh
2026-06-09 20:50 ` Guenter Roeck
2026-05-29 20:31 ` [PATCH 2/5] hwmon: (cros_ec) Prepare the addition of custom groups Thomas Weißschuh
2026-06-09 20:51 ` Guenter Roeck
2026-05-29 20:31 ` [PATCH 3/5] hwmon: (cros_ec) Split out cros_ec_hwmon_get_thermal_config() Thomas Weißschuh
2026-06-09 20:52 ` Guenter Roeck [this message]
2026-05-29 20:31 ` [PATCH 4/5] hwmon: (cros_ec) Add support for displaying fan curves Thomas Weißschuh
2026-06-09 20:53 ` Guenter Roeck
2026-05-29 20:31 ` [PATCH 5/5] hwmon: (cros_ec) Allow modification of " Thomas Weißschuh
2026-05-30 16:37 ` Armin Wolf
2026-06-04 9:04 ` Thomas Weißschuh
2026-06-04 10:33 ` Armin Wolf
2026-06-08 13:34 ` Guenter Roeck
2026-06-08 15:53 ` Thomas Weißschuh
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=2839056c-0827-42ed-9475-e84bed8d18a5@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=skhan@linuxfoundation.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®