From: Guenter Roeck <linux@roeck-us.net>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"'Wim Van Sebroeck'" <wim@iguana.be>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH RESEND 6/7] watchdog: riowd: use devm_kzalloc()
Date: Mon, 29 Apr 2013 11:07:55 -0700 [thread overview]
Message-ID: <20130429180755.GF5183@roeck-us.net> (raw)
In-Reply-To: <001001ce44bc$faf2ce40$f0d86ac0$@samsung.com>
On Mon, Apr 29, 2013 at 06:36:09PM +0900, Jingoo Han wrote:
> Use devm_kzalloc() to make cleanup paths simpler.
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/watchdog/riowd.c | 8 ++------
> 1 files changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/watchdog/riowd.c b/drivers/watchdog/riowd.c
> index 0040451..13363ad 100644
> --- a/drivers/watchdog/riowd.c
> +++ b/drivers/watchdog/riowd.c
> @@ -183,7 +183,7 @@ static int riowd_probe(struct platform_device *op)
> goto out;
>
> err = -ENOMEM;
> - p = kzalloc(sizeof(*p), GFP_KERNEL);
> + p = devm_kzalloc(&op->dev, sizeof(*p), GFP_KERNEL);
> if (!p)
> goto out;
>
That goto is really unnecessary. Just return -ENOMEM and drop the label.
Though that is really another logical change and should be done separately,
so
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> @@ -192,7 +192,7 @@ static int riowd_probe(struct platform_device *op)
> p->regs = of_ioremap(&op->resource[0], 0, 2, DRIVER_NAME);
> if (!p->regs) {
> pr_err("Cannot map registers\n");
> - goto out_free;
> + goto out;
> }
> /* Make miscdev useable right away */
> riowd_device = p;
> @@ -213,9 +213,6 @@ out_iounmap:
> riowd_device = NULL;
> of_iounmap(&op->resource[0], p->regs, 2);
>
> -out_free:
> - kfree(p);
> -
> out:
> return err;
> }
> @@ -226,7 +223,6 @@ static int riowd_remove(struct platform_device *op)
>
> misc_deregister(&riowd_miscdev);
> of_iounmap(&op->resource[0], p->regs, 2);
> - kfree(p);
>
> return 0;
> }
> --
> 1.7.2.5
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-04-29 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 9:36 [PATCH RESEND 6/7] watchdog: riowd: use devm_kzalloc() Jingoo Han
2013-04-29 18:07 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-02 5:51 Jingoo Han
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=20130429180755.GF5183@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/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