From: Jonathan Cameron <jic23@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 1/1] iio: ep93xx: Remove redundant error printing in ep93xx_adc_probe()
Date: Tue, 11 May 2021 15:15:22 +0100 [thread overview]
Message-ID: <20210511151522.4cdafbe9@jic23-huawei> (raw)
In-Reply-To: <20210511113912.5548-1-thunder.leizhen@huawei.com>
On Tue, 11 May 2021 19:39:12 +0800
Zhen Lei <thunder.leizhen@huawei.com> wrote:
> When devm_ioremap_resource() fails, a clear enough error message will be
> printed by its subfunction __devm_ioremap_resource(). The error
> information contains the device name, failure cause, and possibly resource
> information.
>
> Therefore, remove the error printing here to simplify code and reduce the
> binary size.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
Applied to the togreg branch of iio.git and pushed out as testing for
0-day to poke at it.
Thanks,
Jonathan
> ---
> drivers/iio/adc/ep93xx_adc.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/iio/adc/ep93xx_adc.c b/drivers/iio/adc/ep93xx_adc.c
> index c08ab3c6dfafd48..a10a4e8d94fdda8 100644
> --- a/drivers/iio/adc/ep93xx_adc.c
> +++ b/drivers/iio/adc/ep93xx_adc.c
> @@ -165,10 +165,8 @@ static int ep93xx_adc_probe(struct platform_device *pdev)
>
> res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> priv->base = devm_ioremap_resource(&pdev->dev, res);
> - if (IS_ERR(priv->base)) {
> - dev_err(&pdev->dev, "Cannot map memory resource\n");
> + if (IS_ERR(priv->base))
> return PTR_ERR(priv->base);
> - }
>
> iiodev->name = dev_name(&pdev->dev);
> iiodev->modes = INDIO_DIRECT_MODE;
prev parent reply other threads:[~2021-05-11 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 11:39 [PATCH 1/1] iio: ep93xx: Remove redundant error printing in ep93xx_adc_probe() Zhen Lei
2021-05-11 14:15 ` Jonathan Cameron [this message]
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=20210511151522.4cdafbe9@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=thunder.leizhen@huawei.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