From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
elder@kernel.org, tytso@mit.edu,
Namjae Jeon <namjae.jeon@samsung.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com, bpm@sgi.com,
adilger.kernel@dilger.ca, a.sangwan@samsung.com,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/3] xfs: Implement FALLOC_FL_COLLAPSE_RANGE
Date: Fri, 2 Aug 2013 12:44:31 +1000 [thread overview]
Message-ID: <20130802024431.GT13468@dastard> (raw)
In-Reply-To: <20130801082402.GA23414@infradead.org>
On Thu, Aug 01, 2013 at 01:24:02AM -0700, Christoph Hellwig wrote:
> Instead of adding more mess to change_file_space it might be a good idea
> to pull my
>
> "refactor the preallocation and hole punching code"
>
> series from December in first.
You mean this one:
http://oss.sgi.com/archives/xfs/2012-12/msg00124.html
Yeah, probably makes sense to do this. I'll have a look at porting
it forwards to my current tree as xfs_vnodeops.c has gone away in
that series...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
tytso@mit.edu, adilger.kernel@dilger.ca, bpm@sgi.com,
elder@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
xfs@oss.sgi.com, a.sangwan@samsung.com,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH 2/3] xfs: Implement FALLOC_FL_COLLAPSE_RANGE
Date: Fri, 2 Aug 2013 12:44:31 +1000 [thread overview]
Message-ID: <20130802024431.GT13468@dastard> (raw)
In-Reply-To: <20130801082402.GA23414@infradead.org>
On Thu, Aug 01, 2013 at 01:24:02AM -0700, Christoph Hellwig wrote:
> Instead of adding more mess to change_file_space it might be a good idea
> to pull my
>
> "refactor the preallocation and hole punching code"
>
> series from December in first.
You mean this one:
http://oss.sgi.com/archives/xfs/2012-12/msg00124.html
Yeah, probably makes sense to do this. I'll have a look at porting
it forwards to my current tree as xfs_vnodeops.c has gone away in
that series...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2013-08-02 2:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 14:42 [PATCH 2/3] xfs: Implement FALLOC_FL_COLLAPSE_RANGE Namjae Jeon
2013-07-31 14:42 ` Namjae Jeon
2013-07-31 21:11 ` Ben Myers
2013-07-31 21:11 ` Ben Myers
2013-08-01 6:20 ` Namjae Jeon
2013-08-01 6:20 ` Namjae Jeon
2013-08-01 1:18 ` Dave Chinner
2013-08-01 1:18 ` Dave Chinner
2013-08-01 5:33 ` Namjae Jeon
2013-08-01 5:33 ` Namjae Jeon
2013-08-02 3:47 ` Dave Chinner
2013-08-02 3:47 ` Dave Chinner
2013-08-04 8:29 ` Namjae Jeon
2013-08-04 8:29 ` Namjae Jeon
2013-08-01 8:24 ` Christoph Hellwig
2013-08-01 8:24 ` Christoph Hellwig
2013-08-02 2:44 ` Dave Chinner [this message]
2013-08-02 2:44 ` Dave Chinner
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=20130802024431.GT13468@dastard \
--to=david@fromorbit.com \
--cc=a.sangwan@samsung.com \
--cc=adilger.kernel@dilger.ca \
--cc=bpm@sgi.com \
--cc=elder@kernel.org \
--cc=hch@infradead.org \
--cc=linkinjeon@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.com \
/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.