Re: [RFC PATCH v1 1/3] iomap: add ->iomap_next() and iomap_process() helper

[Christoph Hellwig <hch@lst.de>]

> +	/*
> +	 * Produce the next mapping (finishing the previous one if needed).
> +	 * Return 1 to continue iterating, 0 if the range is fully consumed,
> +	 * or a negative error on failure.
> +	 */
> +	int (*iomap_next)(const struct iomap_iter *iter, struct iomap *iomap,
> +			struct iomap *srcmap);

If you add function typedefs for all the other two methods I'd one one here
as well for consistency.  We'll need it anywone once the legacy ops are
entirely gone we can kill of the ops and just pass this function pointer.

As for the arguments:  I don't really see much of a point in passing
the iomap/scrmap separately vs just the iter.  Or am I missing something
here?