From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Ilia Lin <ilia.lin@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Raag Jadav <raag.jadav@intel.com>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] err.h: add ERR_PTR_CONST macro
Date: Thu, 30 Oct 2025 10:27:38 +0200 [thread overview]
Message-ID: <aQMheocySykpTFDN@smile.fi.intel.com> (raw)
In-Reply-To: <69023512.5d0a0220.3cccb7.8e65@mx.google.com>
On Wed, Oct 29, 2025 at 04:38:53PM +0100, Christian Marangi wrote:
> On Wed, Oct 29, 2025 at 05:32:48PM +0200, Andy Shevchenko wrote:
> > 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().
> >
>
> It can't be used for global variables as it does cause compilation
> error.
Can you show an example, please?
> I wanted to use ERR_PTR to set the __smem handle instead of freecode
> (void *) -EPROBE_DEFER and notice the compiler doesn't like using
> ERR_PTR().
>
> Then the problem is clear as static declaration require constant value
> for initialization and ERR_PTR is a inline function.
>
> This is why ERR_PTR_CONST following the pattern that was used for
> FIELD_PREP -> FIELD_PREP_CONST that was also introduced for similar
> case.
>
> So yes this is specific for case of static global variables.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-10-30 8:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 13:33 [PATCH 1/3] err.h: add ERR_PTR_CONST macro Christian Marangi
2025-10-29 13:33 ` [PATCH 2/3] soc: qcom: smem: better track SMEM uninitialized state Christian Marangi
2025-10-29 15:27 ` Andy Shevchenko
2025-10-29 15:32 ` Christian Marangi
2025-10-29 16:11 ` Bjorn Andersson
2025-10-29 13:33 ` [PATCH 3/3] cpufreq: qcom-nvmem: add compatible fallback for ipq806x for no SMEM Christian Marangi
2025-10-29 15:30 ` Andy Shevchenko
2025-10-30 8:56 ` Konrad Dybcio
2025-10-30 10:28 ` Christian Marangi
2025-10-30 10:54 ` Konrad Dybcio
2025-10-30 11:11 ` Christian Marangi
2025-10-30 11:16 ` Konrad Dybcio
2025-10-29 15:32 ` [PATCH 1/3] err.h: add ERR_PTR_CONST macro Andy Shevchenko
2025-10-29 15:38 ` Christian Marangi
2025-10-30 8:27 ` Andy Shevchenko [this message]
2025-10-30 8:37 ` Andy Shevchenko
2025-10-30 10:22 ` Christian Marangi
2025-10-30 14:00 ` Andy Shevchenko
2025-10-30 14:15 ` Arnd Bergmann
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=aQMheocySykpTFDN@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=arnd@arndb.de \
--cc=ilia.lin@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=raag.jadav@intel.com \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).