From: Dave Chinner <david@fromorbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
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, 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
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 [thread overview]
Message-ID: <20140225041346.GA29907@dastard> (raw)
In-Reply-To: <20140225141601.358f6e3df2660d4af44da876@canb.auug.org.au>
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 <david@fromorbit.com> 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
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
viro@zeniv.linux.org.uk, bpm@sgi.com, tytso@mit.edu,
adilger.kernel@dilger.ca, jack@suse.cz, mtk.manpages@gmail.com,
lczerner@redhat.com, linux-fsdevel@vger.kernel.org,
xfs@oss.sgi.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>
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 [thread overview]
Message-ID: <20140225041346.GA29907@dastard> (raw)
In-Reply-To: <20140225141601.358f6e3df2660d4af44da876@canb.auug.org.au>
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 <david@fromorbit.com> 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
next prev parent reply other threads:[~2014-02-25 4:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 16:37 [PATCH v5 0/10] fs: Introduce new flag(FALLOC_FL_COLLAPSE_RANGE) for fallocate Namjae Jeon
2014-02-18 16:37 ` Namjae Jeon
2014-02-24 0:57 ` Dave Chinner
2014-02-24 0:57 ` Dave Chinner
2014-02-24 1:34 ` Namjae Jeon
2014-02-24 1:34 ` Namjae Jeon
2014-02-25 3:16 ` Stephen Rothwell
2014-02-25 3:16 ` Stephen Rothwell
2014-02-25 4:13 ` Dave Chinner [this message]
2014-02-25 4:13 ` Dave Chinner
2014-02-25 23:23 ` Hugh Dickins
2014-02-25 23:23 ` Hugh Dickins
2014-02-25 23:23 ` Hugh Dickins
2014-02-25 23:41 ` Andrew Morton
2014-02-25 23:41 ` Andrew Morton
2014-02-25 23:41 ` Andrew Morton
2014-02-26 1:34 ` Dave Chinner
2014-02-26 1:34 ` Dave Chinner
2014-02-26 1:34 ` Dave Chinner
2014-02-26 1:52 ` Andrew Morton
2014-02-26 1:52 ` Andrew Morton
2014-02-26 1:52 ` Andrew Morton
2014-02-26 3:42 ` Dave Chinner
2014-02-26 3:42 ` Dave Chinner
2014-02-26 3:42 ` Dave Chinner
2014-02-26 1:13 ` Dave Chinner
2014-02-26 1:13 ` Dave Chinner
2014-02-26 1:13 ` Dave Chinner
2014-02-26 4:45 ` Hugh Dickins
2014-02-26 4:45 ` Hugh Dickins
2014-02-26 4:45 ` Hugh Dickins
2014-02-26 6:42 ` Dave Chinner
2014-02-26 6:42 ` Dave Chinner
2014-02-26 6:42 ` Dave Chinner
2014-02-26 23:08 ` Hugh Dickins
2014-02-26 23:08 ` Hugh Dickins
2014-02-26 23:08 ` Hugh Dickins
2014-02-27 1:24 ` Dave Chinner
2014-02-27 1:24 ` Dave Chinner
2014-02-27 1:24 ` Dave Chinner
2014-02-27 1:30 ` Hugh Dickins
2014-02-27 1:30 ` Hugh Dickins
2014-02-27 1:30 ` Hugh Dickins
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=20140225041346.GA29907@dastard \
--to=david@fromorbit.com \
--cc=adilger.kernel@dilger.ca \
--cc=bpm@sgi.com \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linkinjeon@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=namjae.jeon@samsung.com \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--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.