From: Timur Tabi <ttabi@nvidia.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"rdunlap@infradead.org" <rdunlap@infradead.org>
Subject: Re: [PATCH] docs: debugfs: do not recommend debugfs_remove_recursive
Date: Tue, 29 Apr 2025 18:24:40 +0000 [thread overview]
Message-ID: <758ad68deb989eaf8a22ac2bd96915bed77f0f4a.camel@nvidia.com> (raw)
In-Reply-To: <2025042900-emblaze-enlarged-47e8@gregkh>
On Tue, 2025-04-29 at 19:47 +0200, Greg Kroah-Hartman wrote:
> No, the other way around, we should be telling people to use
> debugfs_remove_recursive() instead please, and getting rid of
> debugfs_remove() entirely.
Then why was
#define debugfs_remove_recursive debugfs_remove
added back in 2019, and why was that functionality *added* to debugfs_remove?
I recently added a patch to Nouveau that used debugfs_remove() to clean up all debugfs entries
specifically because it operates recursively.
next prev parent reply other threads:[~2025-04-29 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 17:39 [PATCH] docs: debugfs: do not recommend debugfs_remove_recursive Timur Tabi
2025-04-29 17:47 ` Greg Kroah-Hartman
2025-04-29 18:24 ` Timur Tabi [this message]
2025-04-30 7:30 ` gregkh
2025-04-30 14:27 ` Timur Tabi
2025-04-30 14:57 ` gregkh
2025-04-30 16:36 ` Timur Tabi
2025-04-30 17:10 ` gregkh
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=758ad68deb989eaf8a22ac2bd96915bed77f0f4a.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).