On Fri, 14 Jun 2024 14:43:47 -0700, Darrick J. Wong wrote: > Capture the design of iomap and how to port filesystems to use it. > Apologies for all the rst formatting, but it's necessary to distinguish > code from regular text. > > A lot of this has been collected from various email conversations, code > comments, commit messages, my own understanding of iomap, and > Ritesh/Luis' previous efforts to create a document. Please note a large > part of this has been taken from Dave's reply to last iomap doc > patchset. Thanks to Ritesh, Luis, Dave, Darrick, Matthew, Christoph and > other iomap developers who have taken time to explain the iomap design > in various emails, commits, comments etc. > > [...] Applied to the vfs.iomap branch of the vfs/vfs.git tree. Patches in the vfs.iomap branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs.iomap [1/1] Documentation: the design of iomap and how to port https://git.kernel.org/vfs/vfs/c/549c1f8d490e
