From: Wilken Gottwalt <wilken.gottwalt@posteo.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Ali Ahmet Memis <ali@iusegentoo.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (corsair-psu) serialize debugfs access against hwmon
Date: Thu, 06 Aug 2026 12:19:23 +0000 [thread overview]
Message-ID: <20260806141922.5cf6875a@posteo.net> (raw)
In-Reply-To: <20505360-0780-4f74-8627-8135a40d9401@roeck-us.net>
On Thu, 6 Aug 2026 02:23:16 -0700
Guenter Roeck <linux@roeck-us.net> wrote:
> On 8/5/26 22:23, Wilken Gottwalt wrote:
>
> >
> > That does not even compile on a current 7.1.5/7.1.6 kernel. Though, not sure
> > yet, what that is. But I can not risk running a trunk kernel on my workstation.
> >
> > /usr/lib/modules/7.1.5-arch1-2/build/include/linux/cleanup.h:302:9: error: unknown type name
> > ‘class_hwmon_lock_t’; did you mean ‘class_task_lock_t’? 302 | class_##_name##_t var
> > __cleanup(class_##_name##_destructor) = \ | ^~~~~~
> > /usr/lib/modules/7.1.5-arch1-2/build/include/linux/cleanup.h:422:9: note: in expansion of macro
> > ‘CLASS’ 422 | CLASS(_name, __UNIQUE_ID(guard))
> > | ^~~~~
> > corsair-psu.c:667:9: note: in expansion of macro ‘guard’
> > 667 | guard(hwmon_lock)(priv->hwmon_dev);
> > | ^~~~~
> > corsair-psu.c:667:9: error: cleanup argument not a function
> > 667 | guard(hwmon_lock)(priv->hwmon_dev);
> > | ^~~~~
> >
>
> You'll need commit d1e720c7328e ("hwmon: Support guard() and scoped_guard for subsystem locks").
Oh, I got that confused. I saw the commit was added to Torvalds repo in May.
But I wasn't aware that it is still not part of the official kernel releases.
Ah, I can just add the two lines from the commit to the headers of my local
kernel build files. I will test it.
greetings,
Wilken
next prev parent reply other threads:[~2026-08-06 12:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 12:36 [PATCH] hwmon: (corsair-psu) serialize debugfs access against hwmon Ali Ahmet Memis
2026-08-02 12:57 ` Wilken Gottwalt
2026-08-02 14:07 ` Guenter Roeck
2026-08-03 23:19 ` Guenter Roeck
2026-08-03 23:56 ` Ali Ahmet Memis
2026-08-04 2:54 ` Guenter Roeck
2026-08-04 4:11 ` Wilken Gottwalt
2026-08-04 9:47 ` Ali Ahmet Memis
2026-08-04 10:06 ` Ali Ahmet Memis
2026-08-04 16:34 ` Guenter Roeck
2026-08-04 17:53 ` Wilken Gottwalt
2026-08-04 18:37 ` Wilken Gottwalt
2026-08-04 20:14 ` Guenter Roeck
2026-08-06 5:23 ` Wilken Gottwalt
2026-08-06 9:23 ` Guenter Roeck
2026-08-06 12:19 ` Wilken Gottwalt [this message]
2026-08-06 14:10 ` Wilken Gottwalt
2026-08-06 14:21 ` [PATCH v2] " Ali Ahmet Memis
2026-08-06 15:41 ` 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=20260806141922.5cf6875a@posteo.net \
--to=wilken.gottwalt@posteo.net \
--cc=ali@iusegentoo.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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