aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/sysfs-rules.txt
diff options
context:
space:
mode:
authorHaavard Skinnemoen <haavard.skinnemoen@atmel.com>2008-07-01 15:14:51 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2008-07-21 21:54:59 -0700
commit9505e6375640fc61d92d36c8e9f25a6a218f3f57 (patch)
treedde19254ac9ccd27812aab2c96943bfe2afaf406 /Documentation/sysfs-rules.txt
parentHOWTO: change email addresses of James in HOWTO (diff)
downloadlinux-dev-9505e6375640fc61d92d36c8e9f25a6a218f3f57.tar.xz
linux-dev-9505e6375640fc61d92d36c8e9f25a6a218f3f57.zip
debugfs: Implement debugfs_remove_recursive()
debugfs_remove_recursive() will remove a dentry and all its children. Drivers can use this to zap their whole debugfs tree so that they don't need to keep track of every single debugfs dentry they created. It may fail to remove the whole tree in certain cases: sh-3.2# rmmod atmel-mci < /sys/kernel/debug/mmc0/ios/clock mmc0: card b368 removed atmel_mci atmel_mci.0: Lost dma0chan1, falling back to PIO sh-3.2# ls /sys/kernel/debug/mmc0/ ios But I'm not sure if that case can be handled in any sane manner. Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> Cc: Pierre Ossman <drzeus-list@drzeus.cx> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'Documentation/sysfs-rules.txt')
0 files changed, 0 insertions, 0 deletions