From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>,
Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS reflink and development tip git trees updated
Date: Mon, 19 Sep 2016 21:39:42 -0700 [thread overview]
Message-ID: <20160920043942.GE10172@birch.djwong.org> (raw)
In-Reply-To: <20160919161100.GA19849@infradead.org>
On Mon, Sep 19, 2016 at 09:11:00AM -0700, Christoph Hellwig wrote:
> Can you rebase (and repost the series) on top of the preparations
> in for-next that Dave just pushed out?
>
> That should make reviewing a whole lot easier.
I'm on vacation all week (in the desert with tcp-over-cactus) but I
don't want the reflink review to stall, so here's a branch atop the
for-next branch that Dave announced last night:
https://github.com/djwong/linux/tree/for-dave-for-4.9-3
The scary parts are the rework that I had to do to integrate with hch's
delalloc rewrite. I think all the changes to xfs_file_iomap_begin_delay
are right (the regression tests all pass, at least) but it could use
another set of eyes.
No changes to the userland tools, they're still at:
https://github.com/djwong/xfsprogs/tree/for-dave-for-4.9-2
--D
next prev parent reply other threads:[~2016-09-20 4:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 5:33 XFS reflink and development tip git trees updated Darrick J. Wong
2016-09-09 5:24 ` XFS reflink and getfsmap/scrub development git trees updated again Darrick J. Wong
2016-09-19 16:11 ` XFS reflink and development tip git trees updated Christoph Hellwig
2016-09-19 16:26 ` Darrick J. Wong
2016-09-20 4:39 ` Darrick J. Wong [this message]
2016-09-27 5:23 ` Darrick J. Wong
2016-09-27 14:27 ` Christoph Hellwig
2016-09-27 15:36 ` Darrick J. Wong
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=20160920043942.GE10172@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--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 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).