[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aQIzoGnvZWYuHuoQ@smile.fi.intel.com>
Date: Wed, 29 Oct 2025 17:32:48 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Ilia Lin <ilia.lin@...nel.org>, "Rafael J. Wysocki" <rafael@...nel.org>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	Bjorn Andersson <andersson@...nel.org>,
	Konrad Dybcio <konradybcio@...nel.org>,
	Raag Jadav <raag.jadav@...el.com>, Arnd Bergmann <arnd@...db.de>,
	linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] err.h: add ERR_PTR_CONST macro
On Wed, Oct 29, 2025 at 02:33:19PM +0100, Christian Marangi wrote:
> Add ERR_PTR_CONST macro to initialize global variables with error
ERR_PTR_CONST()
> pointers. This might be useful for specific case where there is a global
> variables initialized to an error condition and then later set to the
> real handle once probe finish/completes.
Okay, this has two caveats:
1) naming is bad as it suggests something about const qualifier (and not, it's
not about that at all);
2) it doesn't explain what's wrong with ERR_PTR().
...
Note, I'm not objecting an idea as a whole.
-- 
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists
 
