[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100322170810.GA30325@oksana.dev.rtsoft.ru>
Date: Mon, 22 Mar 2010 20:08:10 +0300
From: Anton Vorontsov <avorontsov@...mvista.com>
To: Wolfram Sang <w.sang@...gutronix.de>
Cc: kernel-janitors@...r.kernel.org, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, Ryan Mallon <ryan@...ewatersys.com>,
Anton Vorontsov <cbouatmailru@...il.com>
Subject: Re: [PATCH 02/24] power/ds2782: really clear i2c_clientdata on exit
On Sat, Mar 20, 2010 at 03:12:43PM +0100, Wolfram Sang wrote:
> Probably due to a copy & paste bug, clientdata was set again to the data
> structure (which is freed immediately afterwards) when it should be NULLed.
>
> Signed-off-by: Wolfram Sang <w.sang@...gutronix.de>
> Cc: Ryan Mallon <ryan@...ewatersys.com>
> Cc: Anton Vorontsov <cbouatmailru@...il.com>
> ---
> drivers/power/ds2782_battery.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/power/ds2782_battery.c b/drivers/power/ds2782_battery.c
> index da14f37..6971b85 100644
> --- a/drivers/power/ds2782_battery.c
> +++ b/drivers/power/ds2782_battery.c
> @@ -236,7 +236,7 @@ static int ds2782_battery_remove(struct i2c_client *client)
> idr_remove(&battery_id, info->id);
> mutex_unlock(&battery_lock);
>
> - i2c_set_clientdata(client, info);
> + i2c_set_clientdata(client, NULL);
[...]
> - i2c_set_clientdata(client, info);
> + i2c_set_clientdata(client, NULL);
Why is this needed? I'd vote for just removing set_clientdata in
fail/remove paths.
Thanks,
--
Anton Vorontsov
email: cbouatmailru@...il.com
irc://irc.freenode.net/bd2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists