linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Eric W. Biederman" <ebiederm@aristanetworks.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [sysfs] why ->delete_inode() instead of ->clear_inode()?
Date: Sat, 29 May 2010 12:36:25 +0100	[thread overview]
Message-ID: <20100529113625.GO31073@ZenIV.linux.org.uk> (raw)
In-Reply-To: <m1wruni3ut.fsf@fess.ebiederm.org>

On Sat, May 29, 2010 at 12:06:34AM -0700, Eric W. Biederman wrote:

> >From the look of things proc_delete_inode can also be changed to a clear_inode
> method if that is preferred.

Already that way in the local tree, along with quite a few other filesystems...

  reply	other threads:[~2010-05-29 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29  5:43 [sysfs] why ->delete_inode() instead of ->clear_inode()? Al Viro
2010-05-29  7:06 ` Eric W. Biederman
2010-05-29 11:36   ` Al Viro [this message]
2010-05-30  0:45     ` Eric W. Biederman

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=20100529113625.GO31073@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=ebiederm@aristanetworks.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-fsdevel@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).