From: Guenter Roeck <linux@roeck-us.net>
To: Hardware Monitoring <linux-hwmon@vger.kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH 2/4] hwmon: (lm90) Use guard() to acquire subsystem lock
Date: Wed, 13 May 2026 07:25:12 -0700 [thread overview]
Message-ID: <20260513142514.419345-3-linux@roeck-us.net> (raw)
In-Reply-To: <20260513142514.419345-1-linux@roeck-us.net>
Use guard() instead of hwmon_lock() / hwmon_unlock() to acquire and release
the hardware monitoring subsystem lock.
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
drivers/hwmon/lm90.c | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c
index 3c10a5066b53..9ca49abc1a93 100644
--- a/drivers/hwmon/lm90.c
+++ b/drivers/hwmon/lm90.c
@@ -1222,13 +1222,8 @@ static int lm90_update_alarms_locked(struct lm90_data *data, bool force)
static int lm90_update_alarms(struct lm90_data *data, bool force)
{
- int err;
-
- hwmon_lock(data->hwmon_dev);
- err = lm90_update_alarms_locked(data, force);
- hwmon_unlock(data->hwmon_dev);
-
- return err;
+ guard(hwmon_lock)(data->hwmon_dev);
+ return lm90_update_alarms_locked(data, force);
}
static void lm90_alert_work(struct work_struct *__work)
--
2.45.2
next prev parent reply other threads:[~2026-05-13 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 14:25 [PATCH 0/4] hwmon: Support guard() and scoped_guard for subsystem locks Guenter Roeck
2026-05-13 14:25 ` [PATCH 1/4] " Guenter Roeck
2026-05-14 5:46 ` sashiko-bot
2026-05-13 14:25 ` Guenter Roeck [this message]
2026-05-14 6:18 ` [PATCH 2/4] hwmon: (lm90) Use guard() to acquire subsystem lock sashiko-bot
2026-05-13 14:25 ` [PATCH 3/4] hwmon: (ina2xx) Use scoped_guard() to acquire the " Guenter Roeck
2026-05-13 14:25 ` [PATCH 4/4] hwmon: (adt7411) " Guenter Roeck
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=20260513142514.419345-3-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@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