diff options
author | Tejun Heo <tj@kernel.org> | 2013-09-18 17:15:35 -0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-10-03 16:16:43 -0700 |
commit | d69ac5a0bbcf1d9962883fb23e337caf5b38cec8 (patch) | |
tree | 6b9762ddd39b4eec11334886c6907fc9265854d3 /lib/kobject.c | |
parent | 5b8802143a4a3e38906879e78f2c1415c5b3db73 (diff) | |
download | linux-stable-d69ac5a0bbcf1d9962883fb23e337caf5b38cec8.tar.gz linux-stable-d69ac5a0bbcf1d9962883fb23e337caf5b38cec8.tar.bz2 linux-stable-d69ac5a0bbcf1d9962883fb23e337caf5b38cec8.zip |
sysfs: remove sysfs_addrm_cxt->parent_sd
sysfs_addrm_start/finish() enclose sysfs_dirent additions and
deletions and sysfs_addrm_cxt is used to record information necessary
to finish the operations. Currently, sysfs_addrm_start() takes
@parent_sd, records it in sysfs_addrm_cxt, and assumes that all
operations in the block are performed under that @parent_sd.
This assumption has been fine until now but we want to make some
operations behave recursively and, while having @parent_sd recorded in
sysfs_addrm_cxt doesn't necessarily prevents that, it becomes
confusing.
This patch removes sysfs_addrm_cxt->parent_sd and makes
sysfs_add_one() take an explicit @parent_sd parameter. Note that
sysfs_remove_one() doesn't need the extra argument as its parent is
always known from the target @sd.
While at it, add __acquires/releases() notations to
sysfs_addrm_start/finish() respectively.
This patch doesn't make any functional difference.
Signed-off-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/kobject.c')
0 files changed, 0 insertions, 0 deletions