From: Nick Piggin <npiggin@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [rfc][patch 1/3] fs: new truncate sequence
Date: Sat, 15 Aug 2009 17:14:12 +0200 [thread overview]
Message-ID: <20090815151412.GB30951@wotan.suse.de> (raw)
In-Reply-To: <20090815145131.GA25509@infradead.org>
On Sat, Aug 15, 2009 at 10:51:31AM -0400, Christoph Hellwig wrote:
> Nick, what's the plan with moving forward on this? We're badly waiting
> for it on the XFS side.
I was hoping Al would take it but no reply... Any other git tree you
suggest, or -mm?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-08-15 15:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 16:54 [rfc][patch 1/3] fs: new truncate sequence Nick Piggin
2009-07-06 16:55 ` [rfc][patch 2/3] fs: make use of new helper functions Nick Piggin
2009-07-06 17:23 ` Christoph Hellwig
2009-07-06 17:47 ` Nick Piggin
2009-07-06 18:05 ` Miklos Szeredi
2009-07-06 16:56 ` [rfc][patch 3/3] fs: convert ext2,tmpfs to new truncate Nick Piggin
2009-07-06 17:28 ` Christoph Hellwig
2009-07-06 17:59 ` Nick Piggin
2009-07-07 9:17 ` Nick Piggin
2009-07-07 11:45 ` Boaz Harrosh
2009-07-07 13:30 ` Nick Piggin
2009-07-06 17:22 ` [rfc][patch 1/3] fs: new truncate sequence Christoph Hellwig
2009-07-06 17:47 ` Nick Piggin
2009-07-07 7:29 ` Peter Zijlstra
2009-07-07 8:48 ` Nick Piggin
2009-07-06 18:00 ` Miklos Szeredi
2009-07-06 18:10 ` Nick Piggin
2009-07-07 11:45 ` Boaz Harrosh
2009-08-15 14:51 ` Christoph Hellwig
2009-08-15 15:14 ` Nick Piggin [this message]
2009-08-15 15:18 ` Christoph Hellwig
2009-08-15 15:36 ` Nick Piggin
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=20090815151412.GB30951@wotan.suse.de \
--to=npiggin@suse.de \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).