summaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorTimur Tabi <ttabi@nvidia.com>2025-04-29 12:39:58 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-04-30 19:11:04 +0200
commite99efa8ac8fd9cebca99652cb55b277b7200455e (patch)
tree432846afe47e787a541413a3e30687dcc543b8fb /tools/perf/util/scripting-engines/trace-event-python.c
parent0e4965c80ef0f862bff0e2bb6870c8ee118c318e (diff)
docs: debugfs: do not recommend debugfs_remove_recursive
Update the debugfs documentation to indicate that debugfs_remove() should be used to clean up debugfs entries. In commit a3d1e7eb5abe ("simple_recursive_removal(): kernel-side rm -rf for ramfs-style filesystems"), function debugfs_remove_recursive() was made into an alias for debugfs_remove(): #define debugfs_remove_recursive debugfs_remove Therefore, drivers should just use debugfs_remove() going forward. Signed-off-by: Timur Tabi <ttabi@nvidia.com> Link: https://lore.kernel.org/r/20250429173958.3973958-1-ttabi@nvidia.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions