Re: [PATCH v4 0/6] iomap: lift the xfs writepage code into iomap

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH v4 0/6] iomap: lift the xfs writepage code into iomap
From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
Date: Mon, 5 Aug 2019 14:34:49 +0200
Cc: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, Damien Le Moal <Damien.LeMoal@xxxxxxx>
In-reply-to: <20190730144839.GA17025@infradead.org>

On Tue, 30 Jul 2019 at 16:48, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
> I don't really see the point of the split, but the result looks fine
> to me.

The split made it easier for me to debug the gfs2 side by backing out
the xfs changes.

Thanks,
Andreas

References:
- [PATCH v4 0/6] iomap: lift the xfs writepage code into iomap
  - From: Darrick J. Wong
- Re: [PATCH v4 0/6] iomap: lift the xfs writepage code into iomap
  - From: Christoph Hellwig

Prev by Date: Re: [PATCH 2/6] iomap: copy the xfs writeback code to iomap.c
Next by Date: WARNING in __blkdev_put (2)
Previous by thread: Re: [PATCH v4 0/6] iomap: lift the xfs writepage code into iomap
Next by thread: Re: [PATCH v4 0/6] iomap: lift the xfs writepage code into iomap
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux