From: Chris Ball <cjb@laptop.org>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: lars@metafoo.de, viresh.kumar@linaro.org, g.liakhovetski@gmx.de,
gregkh@linuxfoundation.org, yongjun_wei@trendmicro.com.cn,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH -next] mmc: jz4740: fix return value check in jz4740_mmc_probe()
Date: Sat, 24 Aug 2013 22:01:04 -0400 [thread overview]
Message-ID: <87zjs6ttpb.fsf@octavius.laptop.org> (raw)
In-Reply-To: <CAPgLHd9ij8_+Kk7Sjp=5xVwg_t2EjkuhVPKf2C35Y5kRwa=zVA@mail.gmail.com> (Wei Yongjun's message of "Sat, 29 Jun 2013 08:44:53 +0800")
Hi Wei,
On Fri, Jun 28 2013, Wei Yongjun wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> In case of error, the function devm_ioremap_resource() returns ERR_PTR()
> and never returns NULL. The NULL test in the return value check should
> be replaced with IS_ERR(). Also there is already a error message within
> devm_ioremap_resource(), so remove the dev_err call to avoid redundant
> error message.
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> ---
> drivers/mmc/host/jz4740_mmc.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mmc/host/jz4740_mmc.c b/drivers/mmc/host/jz4740_mmc.c
> index 0308c9f..d058f0c 100644
> --- a/drivers/mmc/host/jz4740_mmc.c
> +++ b/drivers/mmc/host/jz4740_mmc.c
> @@ -783,9 +783,8 @@ static int jz4740_mmc_probe(struct platform_device* pdev)
>
> res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> host->base = devm_ioremap_resource(&pdev->dev, res);
> - if (!host->base) {
> - ret = -EBUSY;
> - dev_err(&pdev->dev, "Failed to ioremap base memory\n");
> + if (IS_ERR(host->base)) {
> + ret = PTR_ERR(host->base);
> goto err_free_host;
> }
Thanks, pushed to mmc-next for 3.12.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
prev parent reply other threads:[~2013-08-25 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 0:44 [PATCH -next] mmc: jz4740: fix return value check in jz4740_mmc_probe() Wei Yongjun
2013-08-25 2:01 ` Chris Ball [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=87zjs6ttpb.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=linux-mmc@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=weiyj.lk@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.