From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: nuno.sa@analog.com
Cc: Petr Mladek <pmladek@suse.com>, Chris Down <chris@chrisdown.name>,
John Ogness <john.ogness@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Andi Shyti <andi.shyti@kernel.org>,
Jyoti Bhayana <jbhayana@google.com>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 4/4] iio: common: scmi_iio: convert to dev_err_probe()
Date: Tue, 23 Apr 2024 18:50:27 +0300 [thread overview]
Message-ID: <ZifYwxjNxfM1LwW7@smile.fi.intel.com> (raw)
In-Reply-To: <20240423-dev-add_dev_errp_probe-v2-4-12f43c5d8b0d@analog.com>
On Tue, Apr 23, 2024 at 05:20:33PM +0200, Nuno Sa via B4 Relay wrote:
> From: Nuno Sa <nuno.sa@analog.com>
>
> Make use of dev_err_probe() and dev_err_ptr_probe() to simplify error paths
> during probe.
...
> + return dev_err_ptr_probe(&iiodev->dev, ret,
> + "Error in registering sensor update notifier for sensor %s err %d",
\n
> + sensor->sensor_info->name, ret);
...
> + return dev_err_probe(dev, -EINVAL,
> + "SCMI sensor %d has missing info\n", i);
One line? (It's 99 if you use relaxed limit).
...
> + return dev_err_probe(dev, PTR_ERR(scmi_iio_dev),
> + "failed to allocate IIO device for sensor %s: %ld\n",
> + sensor_info->name, PTR_ERR(scmi_iio_dev));
Please, be sure you remove double error code printing, dev_err_probe() does it
for you already. (This applies to all places like this, if any, in the entire
series.)
...
> + return dev_err_probe(dev, err,
> + "IIO buffer setup error at sensor %s: %d\n",
> + sensor_info->name, err);
Ditto.
...
> + return dev_err_probe(dev, err,
> + "IIO device registration failed at sensor %s: %d\n",
> + sensor_info->name, err);
Ditto.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-04-23 15:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 15:20 [PATCH v2 0/4] dev_printk: add dev_errp_probe() helper Nuno Sa via B4 Relay
2024-04-23 15:20 ` [PATCH v2 1/4] dev_printk: add new dev_err_probe() helpers Nuno Sa via B4 Relay
2024-04-23 15:31 ` Andy Shevchenko
2024-04-23 15:45 ` Andy Shevchenko
2024-05-02 11:54 ` Nuno Sá
2024-05-02 15:37 ` Andy Shevchenko
2024-05-02 11:34 ` Nuno Sá
2024-04-23 15:20 ` [PATCH v2 2/4] iio: temperature: ltc2983: convert to dev_err_probe() Nuno Sa via B4 Relay
2024-04-23 15:42 ` Andy Shevchenko
2024-05-02 11:41 ` Nuno Sá
2024-04-23 15:20 ` [PATCH v2 3/4] iio: backend: make use of dev_err_cast_probe() Nuno Sa via B4 Relay
2024-04-23 15:20 ` [PATCH v2 4/4] iio: common: scmi_iio: convert to dev_err_probe() Nuno Sa via B4 Relay
2024-04-23 15:50 ` Andy Shevchenko [this message]
2024-05-02 11:33 ` Nuno Sá
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=ZifYwxjNxfM1LwW7@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=chris@chrisdown.name \
--cc=gregkh@linuxfoundation.org \
--cc=jbhayana@google.com \
--cc=jic23@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=pmladek@suse.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