From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: "Markus Elfring" <Markus.Elfring@web.de>,
linux-leds@vger.kernel.org,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
"Dan Murphy" <dmurphy@ti.com>, "Pavel Machek" <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] leds-bcm6328: Use devm_platform_ioremap_resource() in bcm6328_leds_probe()
Date: Fri, 20 Sep 2019 21:49:00 +0200 [thread overview]
Message-ID: <72d7c197-e5ca-d51e-4c36-016147ce3d1c@gmail.com> (raw)
In-Reply-To: <bd063a0e-d541-b95f-add1-90edde0acf50@web.de>
Hi Markus,
Thank you for the updated patch set.
Applied to the for-5.5 branch.
Best regards,
Jacek Anaszewski
On 9/20/19 2:40 PM, Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Fri, 20 Sep 2019 14:30:31 +0200
>
> Simplify this function implementation by using a known wrapper function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
>
>
> v2:
>
> Jacek Anaszewski requested to split updates for two modules
>
> into a separate patch for each driver.
>
> https://lore.kernel.org/r/658bd05d-376d-adfd-64a5-e20f83d7b90a@gmail.com/
>
>
>
> drivers/leds/leds-bcm6328.c | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/drivers/leds/leds-bcm6328.c b/drivers/leds/leds-bcm6328.c
> index c50d34e2b098..42e1b7598c3a 100644
> --- a/drivers/leds/leds-bcm6328.c
> +++ b/drivers/leds/leds-bcm6328.c
> @@ -346,16 +346,11 @@ static int bcm6328_leds_probe(struct platform_device *pdev)
> struct device *dev = &pdev->dev;
> struct device_node *np = pdev->dev.of_node;
> struct device_node *child;
> - struct resource *mem_r;
> void __iomem *mem;
> spinlock_t *lock; /* memory lock */
> unsigned long val, *blink_leds, *blink_delay;
>
> - mem_r = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> - if (!mem_r)
> - return -EINVAL;
> -
> - mem = devm_ioremap_resource(dev, mem_r);
> + mem = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(mem))
> return PTR_ERR(mem);
>
> --
> 2.23.0
>
>
next prev parent reply other threads:[~2019-09-20 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 8:55 [PATCH] leds-bcm63xx: Use devm_platform_ioremap_resource() in two functions Markus Elfring
2019-09-19 20:35 ` Jacek Anaszewski
2019-09-20 12:40 ` [PATCH v2] leds-bcm6328: Use devm_platform_ioremap_resource() in bcm6328_leds_probe() Markus Elfring
2019-09-20 19:49 ` Jacek Anaszewski [this message]
2019-09-20 12:50 ` [PATCH v2] leds-bcm6358: Use devm_platform_ioremap_resource() in bcm6358_leds_probe() Markus Elfring
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=72d7c197-e5ca-d51e-4c36-016147ce3d1c@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=dmurphy@ti.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=pavel@ucw.cz \
/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).