On Sat, 12 Apr 2025 10:06:34 +0530, Ritesh Harjani (IBM) wrote: > Let's document the use of these flags in iomap design doc where other > flags are defined too - > > - IOMAP_F_BOUNDARY was added by XFS to prevent merging of I/O and I/O > completions across RTG boundaries. > - IOMAP_F_ATOMIC_BIO was added for supporting atomic I/O operations > for filesystems to inform the iomap that it needs HW-offload based > mechanism for torn-write protection. > > [...] Applied to the vfs-6.16.iomap branch of the vfs/vfs.git tree. Patches in the vfs-6.16.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-6.16.iomap [1/2] Documentation: iomap: Add missing flags description https://git.kernel.org/vfs/vfs/c/336bac5e0892 [2/2] iomap: trace: Add missing flags to [IOMAP_|IOMAP_F_]FLAGS_STRINGS https://git.kernel.org/vfs/vfs/c/d1253c677b8f
