From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
mfasheh@versity.com, akpm@linux-foundation.org,
jlbec@evilplan.org, linux-fsdevel@vger.kernel.org,
ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v3 0/8] ocfs2: wire up {clone, copy, dedupe}_range
Date: Sat, 10 Dec 2016 00:46:54 -0800 [thread overview]
Message-ID: <20161210084654.GA28880@infradead.org> (raw)
In-Reply-To: <20161210015257.GE1555@ZenIV.linux.org.uk>
On Sat, Dec 10, 2016 at 01:52:57AM +0000, 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 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 -> clone fallback in the core
> > to avoid creating annoying merge conflicts.
>
> What was the latest of the patch in question?
https://www.spinics.net/lists/linux-fsdevel/msg104745.html
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
mfasheh@versity.com, akpm@linux-foundation.org,
jlbec@evilplan.org, linux-fsdevel@vger.kernel.org,
ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH v3 0/8] ocfs2: wire up {clone,copy,dedupe}_range
Date: Sat, 10 Dec 2016 00:46:54 -0800 [thread overview]
Message-ID: <20161210084654.GA28880@infradead.org> (raw)
In-Reply-To: <20161210015257.GE1555@ZenIV.linux.org.uk>
On Sat, Dec 10, 2016 at 01:52:57AM +0000, 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 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 -> clone fallback in the core
> > to avoid creating annoying merge conflicts.
>
> What was the latest of the patch in question?
https://www.spinics.net/lists/linux-fsdevel/msg104745.html
next prev parent reply other threads:[~2016-12-10 8:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 0:54 [Ocfs2-devel] [PATCH v3 0/8] ocfs2: wire up {clone, copy, dedupe}_range Darrick J. Wong
2016-12-02 0:54 ` [PATCH v3 0/8] ocfs2: wire up {clone,copy,dedupe}_range Darrick J. Wong
2016-12-02 0:54 ` [Ocfs2-devel] [PATCH 1/8] ocfs2: convert inode refcount test to a helper Darrick J. Wong
2016-12-02 0:54 ` Darrick J. Wong
2016-12-02 0:54 ` [Ocfs2-devel] [PATCH 2/8] ocfs2: add newlines to some error messages Darrick J. Wong
2016-12-02 0:54 ` Darrick J. Wong
2016-12-02 0:54 ` [Ocfs2-devel] [PATCH 3/8] ocfs2: prohibit refcounted swapfiles Darrick J. Wong
2016-12-02 0:54 ` Darrick J. Wong
2016-12-02 0:54 ` [Ocfs2-devel] [PATCH 4/8] ocfs2: budget for extent tree splits when adding refcount flag Darrick J. Wong
2016-12-02 0:54 ` Darrick J. Wong
2016-12-02 0:54 ` [Ocfs2-devel] [PATCH 5/8] ocfs2: don't eat io errors during _dio_end_io_write Darrick J. Wong
2016-12-02 0:54 ` Darrick J. Wong
2016-12-02 0:55 ` [Ocfs2-devel] [PATCH 6/8] ocfs2: always unlock when completing dio writes Darrick J. Wong
2016-12-02 0:55 ` Darrick J. Wong
2016-12-02 0:55 ` [Ocfs2-devel] [PATCH 7/8] ocfs2: implement the VFS clone_range, copy_range, and dedupe_range features Darrick J. Wong
2016-12-02 0:55 ` Darrick J. Wong
2016-12-02 0:55 ` [Ocfs2-devel] [PATCH 8/8] ocfs2: charge quota for reflinked blocks Darrick J. Wong
2016-12-02 0:55 ` Darrick J. Wong
2016-12-09 7:32 ` [Ocfs2-devel] [PATCH v3 0/8] ocfs2: wire up {clone, copy, dedupe}_range Darrick J. Wong
2016-12-09 7:32 ` [PATCH v3 0/8] ocfs2: wire up {clone,copy,dedupe}_range Darrick J. Wong
2016-12-09 8:22 ` [Ocfs2-devel] [PATCH v3 0/8] ocfs2: wire up {clone, copy, dedupe}_range Christoph Hellwig
2016-12-09 8:22 ` [PATCH v3 0/8] ocfs2: wire up {clone,copy,dedupe}_range Christoph Hellwig
2016-12-10 1:52 ` [Ocfs2-devel] [PATCH v3 0/8] ocfs2: wire up {clone, copy, dedupe}_range Al Viro
2016-12-10 1:52 ` [PATCH v3 0/8] ocfs2: wire up {clone,copy,dedupe}_range Al Viro
2016-12-10 8:46 ` Christoph Hellwig [this message]
2016-12-10 8:46 ` Christoph Hellwig
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=20161210084654.GA28880@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=darrick.wong@oracle.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mfasheh@versity.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=viro@ZenIV.linux.org.uk \
/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.