From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f46.google.com ([74.125.82.46]:39584 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752538AbeFFPb1 (ORCPT ); Wed, 6 Jun 2018 11:31:27 -0400 MIME-Version: 1.0 In-Reply-To: References: <20180606104033.4947-1-hch@lst.de> From: =?UTF-8?Q?Andreas_Gr=C3=BCnbacher?= Date: Wed, 6 Jun 2018 17:31:25 +0200 Message-ID: Subject: Re: iomap preparations for GFS2 To: Andreas Gruenbacher Cc: Christoph Hellwig , linux-xfs@vger.kernel.org, Dan Williams , linux-fsdevel , cluster-devel , linux-ext4 Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 2018-06-06 13:38 GMT+02:00 Andreas Gruenbacher : > On 6 June 2018 at 12:40, Christoph Hellwig 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. Thanks, Andreas