From: Jonathan Cameron <jic23@kernel.org>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
"Vladimir Zapolskiy" <vz@mleia.com>,
Marcus Folkesson <marcus.folkesson@gmail.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v2 8/8] iio: dac: ti-dac7311: Make use of the helper function dev_err_probe()
Date: Thu, 7 Oct 2021 18:23:14 +0100 [thread overview]
Message-ID: <20211007182314.6c53158e@jic23-huawei> (raw)
In-Reply-To: <20210928013902.1341-8-caihuoqing@baidu.com>
On Tue, 28 Sep 2021 09:39:01 +0800
Cai Huoqing <caihuoqing@baidu.com> wrote:
> When possible use dev_err_probe help to properly deal with the
> PROBE_DEFER error, the benefit is that DEFER issue will be logged
> in the devices_deferred debugfs file.
> Using dev_err_probe() can reduce code size, and the error value
> gets printed.
>
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
Series applied to the togreg branch of iio.git and pushed out as testing for
0-day to see if it can find any problems before I push this out in a place
where it can make a mess of linux-next
Thanks,
Jonathan
> ---
> drivers/iio/dac/ti-dac7311.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/dac/ti-dac7311.c b/drivers/iio/dac/ti-dac7311.c
> index 9d0b253be841..09218c3029f0 100644
> --- a/drivers/iio/dac/ti-dac7311.c
> +++ b/drivers/iio/dac/ti-dac7311.c
> @@ -266,10 +266,9 @@ static int ti_dac_probe(struct spi_device *spi)
> ti_dac->resolution = spec->resolution;
>
> ti_dac->vref = devm_regulator_get(dev, "vref");
> - if (IS_ERR(ti_dac->vref)) {
> - dev_err(dev, "error to get regulator\n");
> - return PTR_ERR(ti_dac->vref);
> - }
> + if (IS_ERR(ti_dac->vref))
> + return dev_err_probe(dev, PTR_ERR(ti_dac->vref),
> + "error to get regulator\n");
>
> ret = regulator_enable(ti_dac->vref);
> if (ret < 0) {
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-07 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 1:38 [PATCH v2 1/8] iio: dac: ad8801: Make use of the helper function dev_err_probe() Cai Huoqing
2021-09-28 1:38 ` [PATCH v2 2/8] iio: dac: lpc18xx_dac: " Cai Huoqing
2021-09-28 1:38 ` [PATCH v2 3/8] iio: dac: ltc1660: " Cai Huoqing
2021-10-01 7:22 ` Marcus Folkesson
2021-09-28 1:38 ` [PATCH v2 4/8] iio: dac: ds4424: " Cai Huoqing
2021-09-28 1:38 ` [PATCH v2 5/8] iio: dac: max5821: " Cai Huoqing
2021-09-28 1:38 ` [PATCH v2 6/8] iio: dac: mcp4922: " Cai Huoqing
2021-09-28 1:39 ` [PATCH v2 7/8] iio: dac: stm32-dac: " Cai Huoqing
2021-09-28 1:39 ` [PATCH v2 8/8] iio: dac: ti-dac7311: " Cai Huoqing
2021-10-07 17:23 ` Jonathan Cameron [this message]
2021-10-07 17:18 ` [PATCH v2 1/8] iio: dac: ad8801: " Jonathan Cameron
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=20211007182314.6c53158e@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alexandre.torgue@foss.st.com \
--cc=caihuoqing@baidu.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marcus.folkesson@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=vz@mleia.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