[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHc6FU6X29Pr6gA+d0L3WuoCY1XwNjQ9aTYUuAp84-O-ff_xGQ@mail.gmail.com>
Date: Mon, 18 Sep 2017 19:52:32 +0200
From: Andreas Gruenbacher <agruenba@...hat.com>
To: "Theodore Ts'o" <tytso@....edu>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-ext4 <linux-ext4@...r.kernel.org>,
linux-xfs@...r.kernel.org, Jan Kara <jack@...e.cz>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v3 4/4] ext4: Switch to iomap for SEEK_HOLE / SEEK_DATA
On Thu, Sep 14, 2017 at 11:15 PM, Theodore Ts'o <tytso@....edu> wrote:
> On Thu, Sep 14, 2017 at 04:06:19PM +0200, Andreas Gruenbacher wrote:
>> From: Christoph Hellwig <hch@....de>
>>
>> Here we go, after another round of xfstests.
>>
>> The next question, since it touches vfs infrastructure, is which tree
>> this patch queue should be merged through. Al?
>
> Discussions with Darrick before he went on vacation/honeymoon was that
> up until now changes to fs/iomap.c had been going through XFS, but
> since these changes didn't affect XFS, and the rest of the patch
> series touches ext4 and ext4 functionality, that he was OK with
> running this patch series through the ext4 tree.
That sure works for me.
Andreas
Powered by blists - more mailing lists