linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Mukesh Ojha <mojha@codeaurora.org>,
	tglx@linutronix.de, jason@lakedaemon.net,
	yamada.masahiro@socionext.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] irqchip/irq-mvebu-sei: Use devm_platform_ioremap_resource()
Date: Mon, 29 Apr 2019 09:19:14 +0100	[thread overview]
Message-ID: <8dcac5eb-9ff6-1472-9aa1-6878ac5cb172@arm.com> (raw)
In-Reply-To: <1554362413-3305-8-git-send-email-mojha@codeaurora.org>

On 04/04/2019 08:20, Mukesh Ojha wrote:
> devm_platform_ioremap_resource() internally have platform_get_resource()
> and devm_ioremap_resource() in it. So instead of calling them separately
> use devm_platform_ioremap_resource() directly.
> 
> Signed-off-by: Mukesh Ojha <mojha@codeaurora.org>
> ---
>  drivers/irqchip/irq-mvebu-sei.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-mvebu-sei.c b/drivers/irqchip/irq-mvebu-sei.c
> index 18832cc..0a09dcc 100644
> --- a/drivers/irqchip/irq-mvebu-sei.c
> +++ b/drivers/irqchip/irq-mvebu-sei.c
> @@ -382,8 +382,7 @@ static int mvebu_sei_probe(struct platform_device *pdev)
>  	mutex_init(&sei->cp_msi_lock);
>  	raw_spin_lock_init(&sei->mask_lock);
>  
> -	sei->res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> -	sei->base = devm_ioremap_resource(sei->dev, sei->res);
> +	sei->base = devm_platform_ioremap_resource(pdev, 0);
>  	if (IS_ERR(sei->base)) {
>  		dev_err(sei->dev, "Failed to remap SEI resource\n");
>  		return PTR_ERR(sei->base);
> 

Again, what about sei->res?

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2019-04-29  8:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04  7:20 [PATCH 0/7] irqchip: Use devm_platform_ioremap_resource() Mukesh Ojha
2019-04-04  7:20 ` [PATCH 1/7] irqchip/irq-uniphier-aidet: " Mukesh Ojha
2019-04-04  7:20 ` [PATCH 2/7] irqchip/irq-imgpdc.c: " Mukesh Ojha
2019-04-29  8:13   ` Marc Zyngier
2019-04-29  8:24     ` Marc Zyngier
2019-04-04  7:20 ` [PATCH 3/7] irqchip/irq-ts4800.c: " Mukesh Ojha
2019-04-04  7:20 ` [PATCH 4/7] irqchip/irq-mbigen.c: " Mukesh Ojha
2019-04-29  8:16   ` Marc Zyngier
2019-04-04  7:20 ` [PATCH 5/7] irqchip/irq-mvebu-icu: " Mukesh Ojha
2019-04-04  7:20 ` [PATCH 6/7] irqchip/irq-mvebu-pic: " Mukesh Ojha
2019-04-04  7:20 ` [PATCH 7/7] irqchip/irq-mvebu-sei: " Mukesh Ojha
2019-04-29  8:19   ` Marc Zyngier [this message]
2019-04-29  8:27 ` [PATCH 0/7] irqchip: " Marc Zyngier

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=8dcac5eb-9ff6-1472-9aa1-6878ac5cb172@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mojha@codeaurora.org \
    --cc=tglx@linutronix.de \
    --cc=yamada.masahiro@socionext.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).