From: Yang Li <yang.lee@linux.alibaba.com>
To: mdf@kernel.org
Cc: hao.wu@intel.com, yilun.xu@intel.com, trix@redhat.com,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
Yang Li <yang.lee@linux.alibaba.com>
Subject: [PATCH -next 5/6] fpga: manager: Use devm_platform_ioremap_resource()
Date: Thu, 6 Apr 2023 10:34:31 +0800 [thread overview]
Message-ID: <20230406023432.124792-5-yang.lee@linux.alibaba.com> (raw)
In-Reply-To: <20230406023432.124792-1-yang.lee@linux.alibaba.com>
Convert platform_get_resource(), devm_ioremap_resource() to a single
call to devm_platform_ioremap_resource(), as this is exactly what this
function does.
Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
---
drivers/fpga/altera-pr-ip-core-plat.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/fpga/altera-pr-ip-core-plat.c b/drivers/fpga/altera-pr-ip-core-plat.c
index b008a6b8d2d3..a4b26286963b 100644
--- a/drivers/fpga/altera-pr-ip-core-plat.c
+++ b/drivers/fpga/altera-pr-ip-core-plat.c
@@ -15,12 +15,9 @@ static int alt_pr_platform_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
void __iomem *reg_base;
- struct resource *res;
/* First mmio base is for register access */
- res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
-
- reg_base = devm_ioremap_resource(dev, res);
+ reg_base = devm_platform_ioremap_resource(pdev, 0);
if (IS_ERR(reg_base))
return PTR_ERR(reg_base);
--
2.20.1.7.g153144c
next prev parent reply other threads:[~2023-04-06 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 2:34 [PATCH -next 1/6] fpga: manager: Use devm_platform_ioremap_resource() Yang Li
2023-04-06 2:34 ` [PATCH -next 2/6] " Yang Li
2023-04-06 2:34 ` [PATCH -next 3/6] " Yang Li
2023-04-06 2:34 ` [PATCH -next 4/6] fpga: dfl: " Yang Li
2023-04-06 2:34 ` Yang Li [this message]
2023-04-06 2:34 ` [PATCH -next 6/6] fpga: bridge: " Yang Li
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=20230406023432.124792-5-yang.lee@linux.alibaba.com \
--to=yang.lee@linux.alibaba.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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 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.