From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>, reiser@namesys.com
Cc: linux-fsdevel@vger.kernel.org, viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: 2.6.8.1-mm2
Date: Thu, 19 Aug 2004 10:43:42 +0100 [thread overview]
Message-ID: <20040819104342.A7641@infradead.org> (raw)
In-Reply-To: <20040819014204.2d412e9b.akpm@osdl.org>; from akpm@osdl.org on Thu, Aug 19, 2004 at 01:42:04AM -0700
> +reiser4-allow-drop_inode-implementation.patch
> +reiser4-allow-drop_inode-implementation-cleanup.patch
Please don't do this. The only reason reiser4 needs that is because
their broken internal plugin scheme that can't distinguish ->rmdir and
->unlink forces them to reimplement the generic code inside the fs driver.
It's not the kind of functions we want exported.
> +reiser4-export-inode_lock.patch
> +reiser4-export-inode_lock-cleanup.patch
Similarly inode_lock is nothing that should be exported to drivers, it's
too much of an internal that can change - and something drivers can really
badly screw up on.
prev parent reply other threads:[~2004-08-19 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040819014204.2d412e9b.akpm@osdl.org>
2004-08-19 9:39 ` aliased directories, was Re: 2.6.8.1-mm2 Christoph Hellwig
2004-08-19 9:43 ` Christoph Hellwig [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=20040819104342.A7641@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=viro@parcelfarce.linux.theplanet.co.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).