public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: "'Nikolay Balandin'" <n.a.balandin@gmail.com>,
	"'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>
Cc: "'Nikolay Balandin'" <nbalandin@dev.rtsoft.ru>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jingoo Han <jg1.han@samsung.com>,
	"'Bill Pemberton'" <wfp5p@virginia.edu>,
	"'Alexandre Pereira da Silva'" <aletes.xgr@gmail.com>,
	"'Andy Shevchenko'" <andy.shevchenko@gmail.com>,
	"'Wolfram Sang'" <wsa@the-dreams.de>
Subject: Re: [PATCH v3 1/2] drivers/misc: at24: convert to use devm_kzalloc
Date: Wed, 29 May 2013 17:19:03 +0900	[thread overview]
Message-ID: <000701ce5c45$2df28390$89d78ab0$@samsung.com> (raw)
In-Reply-To: <1369771220-5492-1-git-send-email-n.a.balandin@gmail.com>

On Wednesday, May 29, 2013 5:00 AM, Nikolay Balandin wrote:
> 
> From: Nikolay Balandin <nbalandin@dev.rtsoft.ru>
> 
> Use devm_kzalloc to make cleanup paths simpler
> 
> Signed-off-by: Nikolay Balandin <nbalandin@dev.rtsoft.ru>

It looks good.
Reviewed-by: Jingoo Han <jg1.han@samsung.com>

Best regards,
Jingoo Han


> ---
>  drivers/misc/eeprom/at24.c |   44 +++++++++++++++-----------------------------
>  1 file changed, 15 insertions(+), 29 deletions(-)
> 
> diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
> index 2baeec5..5d4fd69 100644
> --- a/drivers/misc/eeprom/at24.c
> +++ b/drivers/misc/eeprom/at24.c
> @@ -492,10 +492,9 @@ static int at24_probe(struct i2c_client *client, const struct i2c_device_id *id)
>  	if (client->dev.platform_data) {
>  		chip = *(struct at24_platform_data *)client->dev.platform_data;
>  	} else {
> -		if (!id->driver_data) {
> -			err = -ENODEV;
> -			goto err_out;
> -		}
> +		if (!id->driver_data)
> +			return -ENODEV;
> +
>  		magic = id->driver_data;
>  		chip.byte_len = BIT(magic & AT24_BITMASK(AT24_SIZE_BYTELEN));
>  		magic >>= AT24_SIZE_BYTELEN;
> @@ -519,8 +518,7 @@ static int at24_probe(struct i2c_client *client, const struct i2c_device_id *id)
>  			"byte_len looks suspicious (no power of 2)!\n");
>  	if (!chip.page_size) {
>  		dev_err(&client->dev, "page_size must not be 0!\n");
> -		err = -EINVAL;
> -		goto err_out;
> +		return -EINVAL;
>  	}
>  	if (!is_power_of_2(chip.page_size))
>  		dev_warn(&client->dev,
> @@ -528,10 +526,9 @@ static int at24_probe(struct i2c_client *client, const struct i2c_device_id *id)
> 
>  	/* Use I2C operations unless we're stuck with SMBus extensions. */
>  	if (!i2c_check_functionality(client->adapter, I2C_FUNC_I2C)) {
> -		if (chip.flags & AT24_FLAG_ADDR16) {
> -			err = -EPFNOSUPPORT;
> -			goto err_out;
> -		}
> +		if (chip.flags & AT24_FLAG_ADDR16)
> +			return -EPFNOSUPPORT;
> +
>  		if (i2c_check_functionality(client->adapter,
>  				I2C_FUNC_SMBUS_READ_I2C_BLOCK)) {
>  			use_smbus = I2C_SMBUS_I2C_BLOCK_DATA;
> @@ -542,8 +539,7 @@ static int at24_probe(struct i2c_client *client, const struct i2c_device_id *id)
>  				I2C_FUNC_SMBUS_READ_BYTE_DATA)) {
>  			use_smbus = I2C_SMBUS_BYTE_DATA;
>  		} else {
> -			err = -EPFNOSUPPORT;
> -			goto err_out;
> +			return -EPFNOSUPPORT;
>  		}
>  	}
> 
> @@ -553,12 +549,10 @@ static int at24_probe(struct i2c_client *client, const struct i2c_device_id *id)
>  		num_addresses =	DIV_ROUND_UP(chip.byte_len,
>  			(chip.flags & AT24_FLAG_ADDR16) ? 65536 : 256);
> 
> -	at24 = kzalloc(sizeof(struct at24_data) +
> +	at24 = devm_kzalloc(&client->dev, sizeof(struct at24_data) +
>  		num_addresses * sizeof(struct i2c_client *), GFP_KERNEL);
> -	if (!at24) {
> -		err = -ENOMEM;
> -		goto err_out;
> -	}
> +	if (!at24)
> +		return -ENOMEM;
> 
>  	mutex_init(&at24->lock);
>  	at24->use_smbus = use_smbus;
> @@ -596,11 +590,10 @@ static int at24_probe(struct i2c_client *client, const struct i2c_device_id *id)
>  			at24->write_max = write_max;
> 
>  			/* buffer (data + address at the beginning) */
> -			at24->writebuf = kmalloc(write_max + 2, GFP_KERNEL);
> -			if (!at24->writebuf) {
> -				err = -ENOMEM;
> -				goto err_struct;
> -			}
> +			at24->writebuf = devm_kzalloc(&client->dev,
> +				write_max + 2, GFP_KERNEL);
> +			if (!at24->writebuf)
> +				return -ENOMEM;
>  		} else {
>  			dev_warn(&client->dev,
>  				"cannot write due to controller restrictions.");
> @@ -648,11 +641,6 @@ err_clients:
>  		if (at24->client[i])
>  			i2c_unregister_device(at24->client[i]);
> 
> -	kfree(at24->writebuf);
> -err_struct:
> -	kfree(at24);
> -err_out:
> -	dev_dbg(&client->dev, "probe error %d\n", err);
>  	return err;
>  }
> 
> @@ -667,8 +655,6 @@ static int at24_remove(struct i2c_client *client)
>  	for (i = 1; i < at24->num_addresses; i++)
>  		i2c_unregister_device(at24->client[i]);
> 
> -	kfree(at24->writebuf);
> -	kfree(at24);
>  	return 0;
>  }
> 
> --
> 1.7.9.5


  reply	other threads:[~2013-05-29  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 20:00 [PATCH v3 1/2] drivers/misc: at24: convert to use devm_kzalloc Nikolay Balandin
2013-05-29  8:19 ` Jingoo Han [this message]
2013-05-29  8:48 ` Andy Shevchenko

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='000701ce5c45$2df28390$89d78ab0$@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=aletes.xgr@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n.a.balandin@gmail.com \
    --cc=nbalandin@dev.rtsoft.ru \
    --cc=wfp5p@virginia.edu \
    --cc=wsa@the-dreams.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox