From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Fabian Frederick <fabf@skynet.be>,
Al Viro <viro@ZenIV.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, neilb@suse.com
Subject: Re: [PATCH 3/6 linux-next] fs/affs: make affs exportable
Date: Fri, 13 Jan 2017 14:03:57 -0500 [thread overview]
Message-ID: <20170113190357.GI24709@fieldses.org> (raw)
In-Reply-To: <20170113185254.GA6092@infradead.org>
On Fri, Jan 13, 2017 at 10:52:54AM -0800, Christoph Hellwig wrote:
> On Fri, Jan 13, 2017 at 12:39:12PM -0500, J. Bruce Fields wrote:
> > If we're going to reject patches that don't implement get_parent (and I
> > think we should), then we should replace "optional but strongly
> > recommended" there by just "mandatory". Any objections?
>
> In theory yes - we'll just need an exception (or dummy implementation)
> for in-memory file systems like tmpfs.
Hm, so does get_parent just never get called for tmpfs because the
parent's always there already?
Should be easy enough to document that exception.
--b.
next prev parent reply other threads:[~2017-01-13 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 21:30 [PATCH 3/6 linux-next] fs/affs: make affs exportable Fabian Frederick
2017-01-03 22:29 ` Al Viro
2017-01-04 5:53 ` Fabian Frederick
2017-01-13 17:39 ` J. Bruce Fields
2017-01-13 18:52 ` Christoph Hellwig
2017-01-13 19:03 ` J. Bruce Fields [this message]
2017-01-13 19:57 ` Al Viro
2017-01-13 20:02 ` J. Bruce Fields
2017-01-04 17:51 ` Fabian Frederick
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=20170113190357.GI24709@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.