From: Chen Gang <gang.chen@asianux.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [Consult] Why need we call device_remove_file() firstly before call device_unregister() ?
Date: Fri, 17 May 2013 13:43:59 +0800 [thread overview]
Message-ID: <5195C39F.9010101@asianux.com> (raw)
Hello All:
I searched 'arch/*' and 'drivers/*' sub-directory, all of them are 'obey
this rule', even in device_unregister() itself, it also firstly calls
device_remove_file(), then call kobject_del().
But after read the related code (fs/sysfs/*, drivers/base/core.c), it
seems kobject_del() -> sysfs_remove_dir() which will release all related
things (can instead of device_remove_file()).
So in fact, we need not call device_remove_file() before call
device_unregister(), is it correct ?
Welcome any member to give a suggestion or completion about it, thanks.
Thanks.
--
Chen Gang
Asianux Corporation
next reply other threads:[~2013-05-17 5:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 5:43 Chen Gang [this message]
2013-05-18 11:06 ` [Consult] Why need we call device_remove_file() firstly before call device_unregister() ? Ming Lei
2013-05-20 1:03 ` Chen Gang
2013-05-20 1:45 ` Greg Kroah-Hartman
2013-05-20 2:12 ` Chen Gang
2013-05-20 2:20 ` Greg Kroah-Hartman
2013-05-20 2:42 ` Chen Gang
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=5195C39F.9010101@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-kernel@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