From: Joel Becker <Joel.Becker@oracle.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 55/58] Make ->drop_inode() just return whether inode needs to be dropped
Date: Tue, 8 Jun 2010 17:24:26 -0700 [thread overview]
Message-ID: <20100609002426.GB6795@mail.oracle.com> (raw)
In-Reply-To: <E1OM7DH-0004g8-Gp@ZenIV.linux.org.uk>
On Tue, Jun 08, 2010 at 11:24:03PM +0100, Al Viro wrote:
>
> ... and let iput_final() do the actual eviction or retention
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This one behaves as ocfs2 wants it to.
Acked-by: Joel Becker <joel.becker@oracle.com>
--
One look at the From:
understanding has blossomed
.procmailrc grows
- Alexander Viro
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-06-09 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 22:24 [PATCH 55/58] Make ->drop_inode() just return whether inode needs to be dropped Al Viro
2010-06-09 0:24 ` Joel Becker [this message]
2010-06-09 1:47 ` [PATCH 55/58][v2] " Al Viro
2010-06-09 15:05 ` [PATCH 55/58] " J. R. Okajima
2010-06-09 22:29 ` Al Viro
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=20100609002426.GB6795@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ftp.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).