[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <550e1dd5-91fb-44ae-bbd5-a10ce1b73ad4@weissschuh.net>
Date: Wed, 30 Oct 2024 12:29:31 -0600 (CST)
From: Thomas Weißschuh <thomas@...ssschuh.net>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>, Len Brown <lenb@...nel.org>
Subject: Re: [PATCH v1 1/1] ACPI: battery: Check for error code from
devm_mutex_init() call
Oct 30, 2024 11:31:21 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>:
> On Wed, Oct 30, 2024 at 10:42:18AM -0600, Thomas Weißschuh wrote:
>> Oct 30, 2024 10:28:03 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>:
>
> ...
>> wouldn't it make sense to mark devm_mutex_init() as __must_check?
>
> It's macro, any idea how to do that for the macros?
It should work on __devm_mutex_init().
I don't think the expression macro in between should interfere.
Unfortunately I can't test it myself right now.
Powered by blists - more mailing lists