[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zy3Za5JvLjk-OYjp@smile.fi.intel.com>
Date: Fri, 8 Nov 2024 11:27:07 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Viresh Kumar <viresh.kumar@...aro.org>,
Huacai Chen <chenhuacai@...nel.org>, loongarch@...ts.linux.dev,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: WANG Xuerui <kernel@...0n.name>,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v2 1/1] cpufreq: loongson3: Check for error code from
devm_mutex_init() call
On Thu, Oct 31, 2024 at 03:46:34PM +0200, Andy Shevchenko wrote:
> Even if it's not critical, the avoidance of checking the error code
> from devm_mutex_init() call today diminishes the point of using devm
> variant of it. Tomorrow it may even leak something. Add the missed
> check.
Any comments? Can this be applied now for fixes, please?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists