From: Jonathan Cameron <jic23@kernel.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: "Joshua Crofts" <joshua.crofts1@gmail.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Alexander Koch" <mail@alexanderkoch.net>,
"Michael Hornung" <mhornung.linux@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/7] iio: light: opt3001: prefer dev_err_probe()
Date: Fri, 22 May 2026 15:07:15 +0100 [thread overview]
Message-ID: <20260522150715.007751fb@jic23-huawei> (raw)
In-Reply-To: <CAKqfh0H5uaQ3AOODBOtT844JLRunVhm11Mxv9Hrgcd7kWs+-mg@mail.gmail.com>
On Fri, 22 May 2026 00:19:16 -0500
Maxwell Doose <m32285159@gmail.com> wrote:
> On Fri, May 22, 2026 at 12:07 AM Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> >
> > On Fri, 22 May 2026 at 03:49, Maxwell Doose <m32285159@gmail.com> wrote:
> > > Ah, but all of the above don't seem like _probe() functions. I'm not
> > > an expert on dev_err_probe() but I'm pretty sure it's only for use (or
> > > at least, designed for use) in _probe() functions. Only function where
> > > I know it's 100% fine in is the one below.
> >
> > Hi Max,
> >
> > Actually if you have any functions that are *only* called in _probe(), then
> > it is okay to move them to dev_err_probe(), you just have to ensure
> > you're not calling dev_err_probe() twice - once in the function and
> > once at the call site.
> >
>
> Ahh, interesting, I never knew that. Thanks for letting me know,
> that's cool. I guess it's more flexible than I thought.
>
> best regards,
> max
opt3001_configure() has a name that makes me think it might well be called
elsewhere (it's not though!). It is probably not worth the churn of
renaming it however.
Jonathan
>
>
> > --
> > Kind regards
> >
> > CJD
next prev parent reply other threads:[~2026-05-22 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 9:55 [PATCH v3 0/7] iio: light: opt3001: driver cleanup Joshua Crofts via B4 Relay
2026-05-21 9:55 ` [PATCH v3 1/7] iio: light: opt3001: move device registration to end of probe() Joshua Crofts via B4 Relay
2026-05-21 10:43 ` Joshua Crofts
2026-05-22 14:03 ` Jonathan Cameron
2026-05-21 9:55 ` [PATCH v3 2/7] iio: light: opt3001: use local struct device and i2c_client variables Joshua Crofts via B4 Relay
2026-05-21 9:55 ` [PATCH v3 3/7] iio: light: opt3001: ensure correct parenthesis alignment Joshua Crofts via B4 Relay
2026-05-22 6:52 ` Maxwell Doose
2026-05-21 9:55 ` [PATCH v3 4/7] iio: light: opt3001: localize for loop iterator Joshua Crofts via B4 Relay
2026-05-21 9:55 ` [PATCH v3 5/7] iio: light: opt3001: prefer dev_err_probe() Joshua Crofts via B4 Relay
2026-05-22 1:48 ` Maxwell Doose
2026-05-22 5:06 ` Joshua Crofts
2026-05-22 5:19 ` Maxwell Doose
2026-05-22 14:07 ` Jonathan Cameron [this message]
2026-05-21 9:55 ` [PATCH v3 6/7] iio: light: opt3001: move driver to guard(mutex)() use Joshua Crofts via B4 Relay
2026-05-21 11:35 ` Joshua Crofts
2026-05-21 9:55 ` [PATCH v3 7/7] iio: light: opt3001: add comment to mutex Joshua Crofts via B4 Relay
2026-05-22 14:12 ` Jonathan Cameron
2026-05-22 14:25 ` Joshua Crofts
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=20260522150715.007751fb@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=mail@alexanderkoch.net \
--cc=mhornung.linux@gmail.com \
--cc=nuno.sa@analog.com \
/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
all inboxes | Powered by JetHome®