From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wl1271: use debugfs_remove_recursive
Date: Fri, 26 Nov 2010 15:44:25 +0200 [thread overview]
Message-ID: <1290779065.15341.15.camel@chilepepper> (raw)
In-Reply-To: <1290595996-2049-1-git-send-email-eliad@wizery.com>
On Wed, 2010-11-24 at 12:53 +0200, ext Eliad Peller wrote:
> Documentation/filesystems/debugfs.txt:
> """
> Once upon a time, debugfs users were required to remember the dentry pointer
> for every debugfs file they created so that all files could be cleaned up.
> We live in more civilized times now, though, and debugfs users can call:
>
> void debugfs_remove_recursive(struct dentry *dentry);
> """
>
> Signed-off-by: Eliad Peller <eliad@wizery.com>
> ---
Applied the series and pushed, thank you!
--
Cheers,
Luca.
prev parent reply other threads:[~2010-11-26 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 10:53 [PATCH 1/2] wl1271: use debugfs_remove_recursive Eliad Peller
2010-11-24 10:53 ` [PATCH 2/2] wl1271: move wl12xx debugfs directory to under wiphy's debugfs Eliad Peller
2010-11-26 13:44 ` Luciano Coelho [this message]
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=1290779065.15341.15.camel@chilepepper \
--to=luciano.coelho@nokia.com \
--cc=eliad@wizery.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).