Thread (14 messages) 14 messages, 3 authors, 2016-02-08

Re: [PATCH 2/3] xfs: don't use ioends for direct write completions

From: Dave Chinner <david@fromorbit.com>
Date: 2016-02-08 09:17:14
Also in: linux-fsdevel, linux-xfs, ocfs2-devel

On Mon, Feb 08, 2016 at 08:31:21AM +0100, Christoph Hellwig wrote:
On Mon, Feb 08, 2016 at 05:17:31PM +1100, Dave Chinner wrote:
quoted
Right now this series is in a stable branch in the XFS tree:

git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git xfs-dio-fix-4.6

If you want to push it through some other tree, please let me know
when/where it is committed so I can rebuild the XFS for-next branch
appropriately from a stable commit/branch...
That's how I think it should be handled.  This would also allow the
ext4 and ocfs2 maintainers to depend on the stable branch to clean
up their direct I/O completion handling in this merge window if they
want to.
I can't tell if you are saying what I've done is fine if the
xfs-dio-fix-4.6 branch is stable (so others can pull it) or whether
it should be in some other tree. Can you clarify, Christoph?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help