Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 12 Jan 2023 09:30:57 +0100
From:   Christoph Hellwig <hch@lst.de>
To:     "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc:     Jeff Layton <jlayton@redhat.com>, linux-fsdevel@vger.kernel.org,
        linux-mm@kvack.org, linux-kernel@vger.kernel.org,
        David Sterba <dsterba@suse.com>
Subject: Re: [PATCH 00/11] Remove AS_EIO and AS_ENOSPC
Message-ID: <20230112083057.GA14077@lst.de>
References: <20230109051823.480289-1-willy@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230109051823.480289-1-willy@infradead.org>
User-Agent: Mutt/1.5.17 (2007-11-01)
Precedence: bulk

On Mon, Jan 09, 2023 at 05:18:12AM +0000, Matthew Wilcox (Oracle) wrote:
> Finish the work of converting every user to the "new" wb_err
> infrastructure.  This will clash with Christoph's patch series to remove
> folio_write_one(), so I'll redo this after that patch series goes in.

Based on the conflicts with the btrfs tree picking up the btrfs part
of this series I think the best way forward is:

 - I'll resubmit my series without the two btrfs patches and the final
   patch to move folio_write_one into jfs
 - that last patch will be delayed until 6.4 and rebased on top of
   your series

While this keeps folio_write_one/write_one_page around for one more
merge window it should entangle all the work nicely.  We'll just need
to watch out that no new users appear.