From: Chanwoo Choi <cw00.choi@samsung.com>
To: anish kumar <anish198519851985@gmail.com>
Cc: gregkh@linuxfoundation.org, myungjoo.ham@samsung.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PATCH] extcon: driver model release call not needed
Date: Sat, 20 Oct 2012 10:57:16 +0900 [thread overview]
Message-ID: <508204FC.4030802@samsung.com> (raw)
In-Reply-To: <1350580326-1574-1-git-send-email-anish198519851985@gmail.com>
On 10/19/2012 02:12 AM, anish kumar wrote:
> From: anish kumar <anish198519851985@gmail.com>
>
> We don't need a release call in this file as we are doing
> everything needed in unregister call and we don't have any
> more pointer to free up.
>
> Signed-off-by: anish kumar <anish198519851985@gmail.com>
> ---
> drivers/extcon/extcon-class.c | 4 +---
> 1 files changed, 1 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/extcon/extcon-class.c b/drivers/extcon/extcon-class.c
> index 946a318..cf30eb1 100644
> --- a/drivers/extcon/extcon-class.c
> +++ b/drivers/extcon/extcon-class.c
> @@ -585,9 +585,7 @@ static void extcon_cleanup(struct extcon_dev *edev, bool skip)
>
> static void extcon_dev_release(struct device *dev)
> {
> - struct extcon_dev *edev = (struct extcon_dev *) dev_get_drvdata(dev);
> -
> - extcon_cleanup(edev, true);
> + /* We don't have any thing to free here */
> }
>
> static const char *muex_name = "mutually_exclusive";
I can't agree this patch. The extcon_dev_release() function is used
for dev->release. If some case without calling extcon_dev_unregister(),
I think dev->release function is needed to free memory of edev->dev.
The edev->dev->release store the function pointer of extcon_dev_release()
in extcon_dev_register().
edev->dev->parent = dev;
edev->dev->class = extcon_class;
edev->dev->release = extcon_dev_release;
Thanks,
Chanwoo Choi
next prev parent reply other threads:[~2012-10-20 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 17:12 anish kumar
2012-10-20 1:57 ` Chanwoo Choi [this message]
2012-10-20 2:30 ` anish kumar
2012-10-20 2:37 ` Chanwoo Choi
2012-10-20 3:33 ` anish kumar
2012-10-20 4:00 ` Chanwoo Choi
2012-10-22 19:57 ` Greg KH
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=508204FC.4030802@samsung.com \
--to=cw00.choi@samsung.com \
--cc=anish198519851985@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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
Powered by JetHome