From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: joshua.crofts1@gmail.com
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] iio: light: opt3001: prefer dev_err_probe()
Date: Mon, 11 May 2026 14:04:03 +0300 [thread overview]
Message-ID: <agG3o3tXt605PBA8@ashevche-desk.local> (raw)
In-Reply-To: <20260511-opt3001-cleanup-v1-3-f7879dc3455c@gmail.com>
On Mon, May 11, 2026 at 12:04:08PM +0200, Joshua Crofts via B4 Relay wrote:
> Switch driver to use dev_err_probe() to unify
> error messages generated in *_probe() and probe path functions.
...
> ret = i2c_smbus_read_word_swapped(opt->client, OPT3001_CONFIGURATION);
> - if (ret < 0) {
> - dev_err(opt->dev, "failed to read register %02x\n",
> - OPT3001_CONFIGURATION);
> - return ret;
> - }
> + if (ret < 0)
> + return dev_err_probe(opt->dev, ret,
We have client available, and here is dev in use. With this being said,
I think the proper order of cleanups is to get rid of dev member and
use local 'dev' variable here
struct device *dev = &opt->client->dev;
> + "failed to read register %02x\n",
> + OPT3001_CONFIGURATION);
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-05-11 11:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 10:04 [PATCH 0/7] iio: light: opt3001: driver cleanup Joshua Crofts via B4 Relay
2026-05-11 10:04 ` [PATCH 1/7] iio: light: opt3001: make headers conform to iwyu Joshua Crofts via B4 Relay
2026-05-11 10:04 ` [PATCH 2/7] iio: light: opt3001: use macros from bits.h header Joshua Crofts via B4 Relay
2026-05-11 11:01 ` Andy Shevchenko
2026-05-11 11:07 ` Joshua Crofts
2026-05-11 13:21 ` Jonathan Cameron
2026-05-11 10:04 ` [PATCH 3/7] iio: light: opt3001: prefer dev_err_probe() Joshua Crofts via B4 Relay
2026-05-11 11:04 ` Andy Shevchenko [this message]
2026-05-11 11:11 ` Joshua Crofts
2026-05-11 10:04 ` [PATCH 4/7] iio: light: opt3001: move driver to guard(mutex)() use Joshua Crofts via B4 Relay
2026-05-11 11:07 ` Andy Shevchenko
2026-05-11 11:09 ` Joshua Crofts
2026-05-11 10:04 ` [PATCH 5/7] iio: light: opt3001: localize for loop iterator Joshua Crofts via B4 Relay
2026-05-11 11:09 ` Andy Shevchenko
2026-05-11 10:04 ` [PATCH 6/7] iio: light: opt3001: remove unnecessary comments Joshua Crofts via B4 Relay
2026-05-11 11:11 ` Andy Shevchenko
2026-05-11 11:14 ` Joshua Crofts
2026-05-11 10:04 ` [PATCH 7/7] iio: light: opt3001: switch driver to managed resources Joshua Crofts via B4 Relay
2026-05-11 11:13 ` Andy Shevchenko
2026-05-11 11:17 ` Joshua Crofts
2026-05-11 13:32 ` Jonathan Cameron
2026-05-11 13:37 ` 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=agG3o3tXt605PBA8@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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