public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Himangi Saraogi <himangi774@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	julia.lawall@lip6.fr
Subject: Re: [PATCH] sbus: Introduce the use of the managed version of kzalloc
Date: Fri, 23 May 2014 22:17:03 +0200	[thread overview]
Message-ID: <20140523201703.GA17295@ravnborg.org> (raw)
In-Reply-To: <20140522203536.GA16457@himangi-Dell>

Hi Himangi.

On Fri, May 23, 2014 at 02:05:36AM +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. The header file is added to make the devm function explicitly
> available. Also, unnecessary assignment statements and labels are
> removed.
> 
> ---
> Not compile tested due to incompatible architecture.
I can confirm that i builds.


> 
> To send to: "David S. Miller" <davem@davemloft.net>,sparclinux@vger.kernel.org,linux-kernel@vger.kernel.org
> 
>  drivers/sbus/char/display7seg.c | 23 ++++++++---------------
>  1 file changed, 8 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/sbus/char/display7seg.c b/drivers/sbus/char/display7seg.c
> index 7c71e7b..367b64d 100644
> --- a/drivers/sbus/char/display7seg.c
> +++ b/drivers/sbus/char/display7seg.c
> @@ -20,6 +20,7 @@
>  #include <asm/io.h>
>  
>  #include <asm/display7seg.h>
> +#include <linux/device.h>
>  
>  #define D7S_MINOR	193
>  #define DRIVER_NAME	"d7s"
> @@ -173,22 +174,21 @@ static struct miscdevice d7s_miscdev = {
>  static int d7s_probe(struct platform_device *op)
>  {
>  	struct device_node *opts;
> -	int err = -EINVAL;
> +	int err;
>  	struct d7s *p;
>  	u8 regs;
>  
>  	if (d7s_device)
> -		goto out;
> +		return -EINVAL;
>  
> -	p = kzalloc(sizeof(*p), GFP_KERNEL);
> -	err = -ENOMEM;
> +	p = devm_kzalloc(&op->dev, sizeof(*p), GFP_KERNEL);
>  	if (!p)
> -		goto out;
> +		return -ENOMEM;
>  
>  	p->regs = of_ioremap(&op->resource[0], 0, sizeof(u8), "d7s");
>  	if (!p->regs) {
>  		printk(KERN_ERR PFX "Cannot map chip registers\n");
> -		goto out_free;
> +		return -ENOMEM;

Can you please explain how it can be correct to return "-ENOMEM",
when we fail to map the chip registers.
Before your patch this resulted in "-EINVAL" - so this is a change in behaviour.


>  	}
>  
>  	err = misc_register(&d7s_miscdev);
> @@ -222,17 +222,11 @@ static int d7s_probe(struct platform_device *op)
>  
>  	dev_set_drvdata(&op->dev, p);
>  	d7s_device = p;
> -	err = 0;
> -
> -out:
> -	return err;
> +	return 0;
>  
>  out_iounmap:
>  	of_iounmap(&op->resource[0], p->regs, sizeof(u8));
> -
> -out_free:
> -	kfree(p);
> -	goto out;
> +	return err;
>  }
It is not am improvement IMO that you replace the nice goto
based error handling with random return points in the code.

	Sam

  reply	other threads:[~2014-05-23 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 20:35 [PATCH] sbus: Introduce the use of the managed version of kzalloc Himangi Saraogi
2014-05-23 20:17 ` Sam Ravnborg [this message]
2014-05-23 20:21   ` Sam Ravnborg
2014-05-24  7:55   ` Julia Lawall

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=20140523201703.GA17295@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davem@davemloft.net \
    --cc=himangi774@gmail.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.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