mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Himangi Saraogi <himangi774@gmail.com>
Cc: Jean Delvare <jdelvare@suse.de>,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
	julia.lawall@lip6.fr
Subject: Re: [PATCH] hwmon: Introduce the use of the managed version of kzalloc
Date: Tue, 20 May 2014 08:51:38 -0700	[thread overview]
Message-ID: <20140520155138.GA23434@roeck-us.net> (raw)
In-Reply-To: <20140518063256.GA7599@himangi-Dell>

On Sun, May 18, 2014 at 12:02:56PM +0530, Himangi Saraogi wrote:
> This patch moves data allocated using kzalloc to managed data allocated
> using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
> functions. Also, the unnecessary label out_free is removed.
> 
> The following Coccinelle semantic patch was used for making the change:
> 
> @platform@
> identifier p, probefn, removefn;
> @@
> struct platform_driver p = {
>   .probe = probefn,
>   .remove = removefn,
> };
> 
> @prb@
> identifier platform.probefn, pdev;
> expression e, e1, e2;
> @@
> probefn(struct platform_device *pdev, ...) {
>   <+...
> - e = kzalloc(e1, e2)
> + e = devm_kzalloc(&pdev->dev, e1, e2)
>   ...
> ?-kfree(e);
>   ...+>
> }
> 
> @rem depends on prb@
> identifier platform.removefn;
> expression e;
> @@
> removefn(...) {
>   <...
> - kfree(e);
>   ...>
> }
> 
> Signed-off-by: Himangi Saraogi <himangi774@gmail.com>
> ---
> Not compile tested.
> 
> To send to: Jean Delvare <jdelvare@suse.de>,Guenter Roeck <linux@roeck-us.net>,
> lm-sensors@lm-sensors.org,linux-kernel@vger.kernel.org
> 
>  drivers/hwmon/ultra45_env.c | 9 +++------
>  1 file changed, 3 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/hwmon/ultra45_env.c b/drivers/hwmon/ultra45_env.c
> index fb3e693..92564b8 100644
> --- a/drivers/hwmon/ultra45_env.c
> +++ b/drivers/hwmon/ultra45_env.c
> @@ -252,7 +252,7 @@ static const struct attribute_group env_group = {
>  
>  static int env_probe(struct platform_device *op)
>  {
> -	struct env *p = kzalloc(sizeof(*p), GFP_KERNEL);
> +	struct env *p = devm_kzalloc(&op->dev, sizeof(*p), GFP_KERNEL);
>  	int err = -ENOMEM;
>  
>  	if (!p)
> @@ -262,7 +262,7 @@ static int env_probe(struct platform_device *op)
>  
>  	p->regs = of_ioremap(&op->resource[0], 0, REG_SIZE, "pic16f747");
>  	if (!p->regs)
> -		goto out_free;
> +		goto out;
>  
>  	err = sysfs_create_group(&op->dev.kobj, &env_group);
>  	if (err)
> @@ -285,9 +285,7 @@ out_sysfs_remove_group:
>  
>  out_iounmap:
>  	of_iounmap(&op->resource[0], p->regs, REG_SIZE);
> -
> -out_free:
> -	kfree(p);
> +	
>  	goto out;
>  }

This introduces a whitespace error, and results in really ugly code.

        err = 0;

out:
        return err;

out_sysfs_remove_group:
        sysfs_remove_group(&op->dev.kobj, &env_group);

out_iounmap:
	of_iounmap(&op->resource[0], p->regs, REG_SIZE);

	goto out;
}

Ok, the code is already ugly, but it doesn't make sense to me
to spend time on it without cleaning it up.

Guenter

      reply	other threads:[~2014-05-20 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-18  6:32 Himangi Saraogi
2014-05-20 15:51 ` Guenter Roeck [this message]

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=20140520155138.GA23434@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=himangi774@gmail.com \
    --cc=jdelvare@suse.de \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    /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®