From: Nick Piggin <npiggin@suse.de>
To: Jan Kara <jack@suse.cz>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [patch 2/5] fs: convert simple fs to new truncate
Date: Thu, 10 Dec 2009 16:15:38 +1100 [thread overview]
Message-ID: <20091210051538.GB15787@nick> (raw)
In-Reply-To: <20091209143945.GB7044@quack.suse.cz>
On Wed, Dec 09, 2009 at 03:39:45PM +0100, Jan Kara wrote:
> On Tue 08-12-09 09:39:57, Nick Piggin wrote:
> > Convert simple filesystems: ramfs, configfs, sysfs, block_dev to new truncate
> > sequence.
> >
> > Signed-off-by: Nick Piggin <npiggin@suse.de>
> Looks good.
> Acked-by: Jan Kara <jack@suse.cz>
Thanks.
Al, any chance to merge patches 1 and 2 upstream early in this round? They
should be fairly non intrusive and back compatible. Then I can get the
filesystem specific patches to their maintainers and you won't have to
bother with them.
ecryptfs is being fixed to use notify_change rather than vmtruncate (which
is anyway buggy today), so that won't be a problem.
I think we'll be able to get rid of old protocol completely within just
a couple of releases. Jan and Christoph have made pretty good progress
there.
next prev parent reply other threads:[~2009-12-10 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 8:38 [patch 1/5] fs: truncate introduce new sequence Nick Piggin
2009-12-08 8:39 ` [patch 2/5] fs: convert simple fs to new truncate Nick Piggin
2009-12-09 14:39 ` Jan Kara
2009-12-10 5:15 ` Nick Piggin [this message]
2009-12-10 8:44 ` Boaz Harrosh
2009-12-10 7:57 ` Nick Piggin
2009-12-08 8:41 ` [patch 3/5] tmpfs: convert to use the new truncate convention Nick Piggin
2009-12-09 14:45 ` Jan Kara
2009-12-10 0:48 ` Nick Piggin
2009-12-08 8:42 ` [patch 4/5] ext2: " Nick Piggin
2009-12-09 14:57 ` Jan Kara
2009-12-10 1:11 ` Nick Piggin
2009-12-10 10:20 ` Jan Kara
2009-12-08 8:43 ` [patch 5/5] fat: " Nick Piggin
2009-12-09 15:08 ` Jan Kara
2009-12-09 14:38 ` [patch 1/5] fs: truncate introduce new sequence Jan Kara
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=20091210051538.GB15787@nick \
--to=npiggin@suse.de \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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 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).