From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] hwmon fixes for v6.17-rc5
Date: Fri, 5 Sep 2025 09:58:35 -0700 [thread overview]
Message-ID: <20250905165835.1653373-1-linux@roeck-us.net> (raw)
Hi Linus,
Please pull hwmon fixes for Linux v6.17-rc5 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-v6.17-rc5
Thanks,
Guenter
------
The following changes since commit 1b237f190eb3d36f52dffe07a40b5eb210280e00:
Linux 6.17-rc3 (2025-08-24 12:04:12 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git tags/hwmon-for-v6.17-rc5
for you to fetch changes up to c2623573178bab32990695fb729e9b69710ed66d:
hwmon: (ina238) Correctly clamp power limits (2025-09-01 08:03:05 -0700)
----------------------------------------------------------------
hwmon fixes for v6.17-rc5
- ina238: Various value range fixes when writing limit attributes
- mlxreg-fan: Prevent fans from getting stuck at 0 RPM
----------------------------------------------------------------
Chris Packham (1):
hwmon: (ina238) Correctly clamp temperature
Guenter Roeck (2):
hwmon: (ina238) Correctly clamp shunt voltage limit
hwmon: (ina238) Correctly clamp power limits
Vadim Pasternak (1):
hwmon: mlxreg-fan: Prevent fans from getting stuck at 0 RPM
drivers/hwmon/ina238.c | 9 +++++----
drivers/hwmon/mlxreg-fan.c | 5 ++---
2 files changed, 7 insertions(+), 7 deletions(-)
next reply other threads:[~2025-09-05 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 16:58 Guenter Roeck [this message]
2025-09-05 20:17 ` [GIT PULL] hwmon fixes for v6.17-rc5 pr-tracker-bot
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=20250905165835.1653373-1-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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