On Sat, Dec 10, 2016 at 01:52:57AM +, Al Viro wrote:
> On Fri, Dec 09, 2016 at 12:22:53AM -0800, Christoph Hellwig wrote:
> > On Thu, Dec 08, 2016 at 11:32:13PM -0800, Darrick J. Wong wrote:
> > > It's been a week and nobody's written in any objections. Andrew, could
> > > this go into
On Fri, Dec 09, 2016 at 12:22:53AM -0800, Christoph Hellwig wrote:
> On Thu, Dec 08, 2016 at 11:32:13PM -0800, Darrick J. Wong wrote:
> > It's been a week and nobody's written in any objections. Andrew, could
> > this go into linux-next for some soak time?
>
> I'm mostly fine with my series, but
On Thu, Dec 08, 2016 at 11:32:13PM -0800, Darrick J. Wong wrote:
> It's been a week and nobody's written in any objections. Andrew, could
> this go into linux-next for some soak time?
I'm mostly fine with my series, but I would much prefer if this went
on top of my patch to implement the copy ->
On Thu, Dec 01, 2016 at 04:54:22PM -0800, Darrick J. Wong wrote:
> Hi all,
>
> This is the third submission of a series of patches that wire up the
> existing ocfs2 reflinking capabilities to the new(ish) VFS
> {copy,clone,dedupe}_range interface. The first few patches clean up
> some minor bugs
Hi all,
This is the third submission of a series of patches that wire up the
existing ocfs2 reflinking capabilities to the new(ish) VFS
{copy,clone,dedupe}_range interface. The first few patches clean up
some minor bugs that I found; the last kernel patch contains the new
code. The last patch
