From: Fabio Estevam <fabio.estevam@freescale.com>
To: <k.debski@samsung.com>
Cc: <m.chehab@samsung.com>, <kernel@pengutronix.de>,
<linux-media@vger.kernel.org>,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: [PATCH v4 3/3] [media] coda: No need to check the return value of platform_get_resource()
Date: Tue, 23 Jul 2013 15:04:50 -0300 [thread overview]
Message-ID: <1374602690-12842-3-git-send-email-fabio.estevam@freescale.com> (raw)
In-Reply-To: <1374602690-12842-1-git-send-email-fabio.estevam@freescale.com>
When using devm_ioremap_resource(), we do not need to check the return value of
platform_get_resource(), so just remove it.
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
---
Changes since v3:
- None
Changes since v2:
- None
Changes since v1:
- None
drivers/media/platform/coda.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/drivers/media/platform/coda.c b/drivers/media/platform/coda.c
index 2d1576b..4a0a421 100644
--- a/drivers/media/platform/coda.c
+++ b/drivers/media/platform/coda.c
@@ -2049,11 +2049,6 @@ static int coda_probe(struct platform_device *pdev)
/* Get memory for physical registers */
res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
- if (res == NULL) {
- dev_err(&pdev->dev, "failed to get memory region resource\n");
- return -ENOENT;
- }
-
dev->regs_base = devm_ioremap_resource(&pdev->dev, res);
if (IS_ERR(dev->regs_base))
return PTR_ERR(dev->regs_base);
--
1.8.1.2
next prev parent reply other threads:[~2013-07-23 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 18:04 [PATCH v4 1/3] [media] coda: Fix error paths Fabio Estevam
2013-07-23 18:04 ` [PATCH v4 2/3] [media] coda: Check the return value from clk_prepare_enable() Fabio Estevam
2013-07-23 18:04 ` Fabio Estevam [this message]
2013-07-24 9:47 ` [PATCH v4 1/3] [media] coda: Fix error paths Philipp Zabel
2013-08-01 15:27 ` Kamil Debski
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=1374602690-12842-3-git-send-email-fabio.estevam@freescale.com \
--to=fabio.estevam@freescale.com \
--cc=k.debski@samsung.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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;
as well as URLs for NNTP newsgroup(s).