[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 6 Jun 2018 17:39:55 +0200
From: Christoph Hellwig <hch@....de>
To: Andreas Grünbacher
<andreas.gruenbacher@...il.com>
Cc: Andreas Gruenbacher <agruenba@...hat.com>,
Christoph Hellwig <hch@....de>, linux-xfs@...r.kernel.org,
Dan Williams <dan.j.williams@...el.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
cluster-devel <cluster-devel@...hat.com>,
linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: iomap preparations for GFS2
On Wed, Jun 06, 2018 at 05:31:25PM +0200, Andreas Grünbacher wrote:
> 2018-06-06 13:38 GMT+02:00 Andreas Gruenbacher <agruenba@...hat.com>:
> > On 6 June 2018 at 12:40, Christoph Hellwig <hch@....de> wrote:
> >> Hi all,
> >>
> >> this is a slight rework of the patches from Andreas to prepare for gfs2
> >> using the iomap code. I'd like to start with an immutable branch for
> >> iomap patches in either the XFS tree or a tree of mine own with something
> >> like this so that we can have a nice common base for both the major
> >> iomap changes for XFS and the GFS2 work.
>
> When do you want to push this upstream? We've got the gfs2 patches
> that depend on it, and we cannot make progress with those before this
> set is pushed.
As soon as we have 4.18r-c1 can start work for the next merge
window.
Powered by blists - more mailing lists