From: Greg KH <gregkh@linuxfoundation.org>
To: anish kumar <anish198519851985@gmail.com>
Cc: myungjoo.ham@samsung.com, cw00.choi@samsung.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PATCH] extcon: driver model release call not needed
Date: Mon, 22 Oct 2012 12:57:30 -0700 [thread overview]
Message-ID: <20121022195730.GB13640@kroah.com> (raw)
In-Reply-To: <1350580326-1574-1-git-send-email-anish198519851985@gmail.com>
On Fri, Oct 19, 2012 at 02:12:06AM +0900, 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 */
> }
In the future (I know you fixed this up), doing an empty release()
function will get you in big trouble. Please read the kobject
documentation for more information about why this is.
greg k-h
prev parent reply other threads:[~2012-10-22 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 17:12 [PATCH] [PATCH] extcon: driver model release call not needed anish kumar
2012-10-20 1:57 ` Chanwoo Choi
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 [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=20121022195730.GB13640@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anish198519851985@gmail.com \
--cc=cw00.choi@samsung.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.