mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: cgel.zte@gmail.com, bp@alien8.de, mchehab@kernel.org
Cc: tony.luck@intel.com, james.morse@arm.com, rric@kernel.org,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lv Ruyi <lv.ruyi@zte.com.cn>, Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] edac: Make use of the helper function devm_platform_ioremap_resource()
Date: Thu, 21 Apr 2022 11:00:17 +0200	[thread overview]
Message-ID: <3f092daad178f60e021784d3e398288e15fda4b6.camel@pengutronix.de> (raw)
In-Reply-To: <20220421084621.2615517-1-lv.ruyi@zte.com.cn>

On Thu, 2022-04-21 at 08:46 +0000, cgel.zte@gmail.com wrote:
> From: Lv Ruyi <lv.ruyi@zte.com.cn>
> 
> Use the devm_platform_ioremap_resource() helper instead of calling
> platform_get_resource() and devm_ioremap_resource() separately.Make the
> code simpler without functional changes.
> 
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Lv Ruyi <lv.ruyi@zte.com.cn>

Reviewed-by: Jan Luebbe <jlu@pengutronix.de>

Thanks,
Jan

> ---
>  drivers/edac/armada_xp_edac.c | 18 ++----------------
>  1 file changed, 2 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/edac/armada_xp_edac.c b/drivers/edac/armada_xp_edac.c
> index b1f46a974b9e..038abbb83f4b 100644
> --- a/drivers/edac/armada_xp_edac.c
> +++ b/drivers/edac/armada_xp_edac.c
> @@ -286,17 +286,10 @@ static int axp_mc_probe(struct platform_device *pdev)
>  	struct edac_mc_layer layers[1];
>  	const struct of_device_id *id;
>  	struct mem_ctl_info *mci;
> -	struct resource *r;
>  	void __iomem *base;
>  	uint32_t config;
>  
> -	r = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> -	if (!r) {
> -		dev_err(&pdev->dev, "Unable to get mem resource\n");
> -		return -ENODEV;
> -	}
> -
> -	base = devm_ioremap_resource(&pdev->dev, r);
> +	base = devm_platform_ioremap_resource(pdev, 0);
>  	if (IS_ERR(base)) {
>  		dev_err(&pdev->dev, "Unable to map regs\n");
>  		return PTR_ERR(base);
> @@ -516,15 +509,8 @@ static int aurora_l2_probe(struct platform_device *pdev)
>  	const struct of_device_id *id;
>  	uint32_t l2x0_aux_ctrl;
>  	void __iomem *base;
> -	struct resource *r;
> -
> -	r = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> -	if (!r) {
> -		dev_err(&pdev->dev, "Unable to get mem resource\n");
> -		return -ENODEV;
> -	}
>  
> -	base = devm_ioremap_resource(&pdev->dev, r);
> +	base = devm_platform_ioremap_resource(pdev, 0);
>  	if (IS_ERR(base)) {
>  		dev_err(&pdev->dev, "Unable to map regs\n");
>  		return PTR_ERR(base);

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2022-04-21  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  8:46 cgel.zte
2022-04-21  9:00 ` Jan Lübbe [this message]
2022-04-29  9:20 ` Borislav Petkov

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=3f092daad178f60e021784d3e398288e15fda4b6.camel@pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=bp@alien8.de \
    --cc=cgel.zte@gmail.com \
    --cc=james.morse@arm.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.ruyi@zte.com.cn \
    --cc=mchehab@kernel.org \
    --cc=rric@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=zealci@zte.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®