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.8-rc3
Date: Fri, 2 Feb 2024 10:30:12 -0800 [thread overview]
Message-ID: <20240202183012.1607147-1-linux@roeck-us.net> (raw)
Hi Linus,
Please pull hwmon fixes for Linux v6.8-rc3 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-v6.8-rc3
Thanks,
Guenter
------
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git tags/hwmon-for-v6.8-rc3
for you to fetch changes up to 915644189c22d9c93e9fee7c7c993b58e745bef7:
hwmon: (pmbus/mp2975) Correct comment inside 'mp2975_read_byte_data' (2024-01-27 08:03:18 -0800)
----------------------------------------------------------------
hwmon fixes for v6.8-rc3
- pmbus/mp2975: Fix driver initialization
- gigabyte_waterforce: Add missing unlock in error handling path
----------------------------------------------------------------
Harshit Mogalapalli (1):
hwmon: gigabyte_waterforce: Fix locking bug in waterforce_get_status()
Konstantin Aladyshev (2):
hwmon: (pmbus/mp2975) Fix driver initialization for MP2975 device
hwmon: (pmbus/mp2975) Correct comment inside 'mp2975_read_byte_data'
drivers/hwmon/gigabyte_waterforce.c | 2 +-
drivers/hwmon/pmbus/mp2975.c | 16 ++++++++++++++++
2 files changed, 17 insertions(+), 1 deletion(-)
next reply other threads:[~2024-02-02 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 18:30 Guenter Roeck [this message]
2024-02-02 21:00 ` [GIT PULL] hwmon fixes for v6.8-rc3 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=20240202183012.1607147-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