From: Grant Likely <grant.likely@secretlab.ca>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Linus Walleij <linus.walleij@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: mvebu: Don't free chip label memory
Date: Mon, 14 Jan 2013 14:15:04 +0000 [thread overview]
Message-ID: <20130114141504.C91503E232D@localhost> (raw)
In-Reply-To: <1358160800-12185-1-git-send-email-thierry.reding@avionic-design.de>
On Mon, 14 Jan 2013 11:53:20 +0100, Thierry Reding <thierry.reding@avionic-design.de> wrote:
> The gpio_chip.label field is a const char * and assigned the value of a
> call to dev_name(). Memory obtained from dev_name() should not be freed
> by drivers.
>
> Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
Linus, can you put this in your fixes branch?
Thanks,
g.
> ---
> drivers/gpio/gpio-mvebu.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
> index 7d9bd94..6819d63 100644
> --- a/drivers/gpio/gpio-mvebu.c
> +++ b/drivers/gpio/gpio-mvebu.c
> @@ -547,7 +547,6 @@ static int mvebu_gpio_probe(struct platform_device *pdev)
> mvchip->membase = devm_request_and_ioremap(&pdev->dev, res);
> if (! mvchip->membase) {
> dev_err(&pdev->dev, "Cannot ioremap\n");
> - kfree(mvchip->chip.label);
> return -ENOMEM;
> }
>
> @@ -557,14 +556,12 @@ static int mvebu_gpio_probe(struct platform_device *pdev)
> res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> if (! res) {
> dev_err(&pdev->dev, "Cannot get memory resource\n");
> - kfree(mvchip->chip.label);
> return -ENODEV;
> }
>
> mvchip->percpu_membase = devm_request_and_ioremap(&pdev->dev, res);
> if (! mvchip->percpu_membase) {
> dev_err(&pdev->dev, "Cannot ioremap\n");
> - kfree(mvchip->chip.label);
> return -ENOMEM;
> }
> }
> @@ -625,7 +622,6 @@ static int mvebu_gpio_probe(struct platform_device *pdev)
> mvchip->irqbase = irq_alloc_descs(-1, 0, ngpios, -1);
> if (mvchip->irqbase < 0) {
> dev_err(&pdev->dev, "no irqs\n");
> - kfree(mvchip->chip.label);
> return -ENOMEM;
> }
>
> @@ -633,7 +629,6 @@ static int mvebu_gpio_probe(struct platform_device *pdev)
> mvchip->membase, handle_level_irq);
> if (! gc) {
> dev_err(&pdev->dev, "Cannot allocate generic irq_chip\n");
> - kfree(mvchip->chip.label);
> return -ENOMEM;
> }
>
> @@ -668,7 +663,6 @@ static int mvebu_gpio_probe(struct platform_device *pdev)
> irq_remove_generic_chip(gc, IRQ_MSK(ngpios), IRQ_NOREQUEST,
> IRQ_LEVEL | IRQ_NOPROBE);
> kfree(gc);
> - kfree(mvchip->chip.label);
> return -ENODEV;
> }
>
> --
> 1.8.1
>
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
next prev parent reply other threads:[~2013-01-14 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 10:53 [PATCH] gpio: mvebu: Don't free chip label memory Thierry Reding
2013-01-14 14:15 ` Grant Likely [this message]
2013-01-17 11:27 ` Linus Walleij
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=20130114141504.C91503E232D@localhost \
--to=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.reding@avionic-design.de \
/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.