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]

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>
References: <156444945993.2682261.3926017251626679029.stgit@magnolia> <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: Re: [PATCH 1/5] xfs: use a struct iomap in xfs_writepage_ctx
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] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux