From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Chinner Subject: Re: [PATCH v5 0/10] fs: Introduce new flag(FALLOC_FL_COLLAPSE_RANGE) for fallocate Date: Tue, 25 Feb 2014 15:13:46 +1100 Message-ID: <20140225041346.GA29907@dastard> References: <1392741436-19995-1-git-send-email-linkinjeon@gmail.com> <20140224005710.GH4317@dastard> <20140225141601.358f6e3df2660d4af44da876@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Namjae Jeon , tytso@mit.edu, Namjae Jeon , linux-kernel@vger.kernel.org, xfs@oss.sgi.com, bpm@sgi.com, adilger.kernel@dilger.ca, viro@zeniv.linux.org.uk, lczerner@redhat.com, linux-fsdevel@vger.kernel.org, jack@suse.cz, linux-ext4@vger.kernel.org, mtk.manpages@gmail.com To: Stephen Rothwell Return-path: Content-Disposition: inline In-Reply-To: <20140225141601.358f6e3df2660d4af44da876@canb.auug.org.au> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org On Tue, Feb 25, 2014 at 02:16:01PM +1100, Stephen Rothwell wrote: > Hi Dave, > > On Mon, 24 Feb 2014 11:57:10 +1100 Dave Chinner wrote: > > > > > Namjae Jeon (10): > > > fs: Add new flag(FALLOC_FL_COLLAPSE_RANGE) for fallocate > > > xfs: Add support FALLOC_FL_COLLAPSE_RANGE for fallocate > > > > I've pushed these to the following branch: > > > > git://oss.sgi.com/xfs/xfs.git xfs-collapse-range > > > > And so they'll be in tomorrow's linux-next tree. > > > > > ext4: Add support FALLOC_FL_COLLAPSE_RANGE for fallocate > > > > I've left this one alone for the ext4 guys to sort out. > > So presumably that xfs tree branch is now completely stable and so Ted > could just merge that branch into the ext4 tree as well and put the ext4 > part on top of that in his tree. Well, for some definition of stable. Right now it's just a topic branch that is merged into the for-next branch, so in theory it is still just a set of pending changes in a branch in a repo that has been pushed to linux-next for testing. That said, I don't see that branch changing unless we find bugs in the code or a problem with the API needs fixing, at which point I would add more commits to it and rebase the for-next branch that you are pulling into the linux-next tree. Realistically, I'm waiting for Lukas to repost his other pending fallocate changes (the zero range changes) so I can pull the VFS and XFS bits of that into the XFS tree and I can test them together before I'll call the xfs-collapse-range stable and ready to be merged into some other tree... Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs