Al Viro 5a19095103 use less confusing names for iov_iter direction initializers ... [ Upstream commit de4eda9de2 ] READ/WRITE proved to be actively confusing - the meanings are "data destination, as used with read(2)" and "data source, as used with write(2)", but people keep interpreting those as "we read data from it" and "we write data to it", i.e. exactly the wrong way. Call them ITER_DEST and ITER_SOURCE - at least that is harder to misinterpret... Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Stable-dep-of: 6dd88fd59d ("vhost-scsi: unbreak any layout for response") Signed-off-by: Sasha Levin <sashal@kernel.org>		2023-02-09 11:28:04 +01:00
..
Kconfig	…
Makefile	…
acl.c	…
acl.h	…
cache.c	…
cache.h	…
fid.c	9p: Fix some kernel-doc comments	2022-07-02 18:52:21 +09:00
fid.h	…
v9fs.c	…
v9fs.h	…
v9fs_vfs.h	…
vfs_addr.c	use less confusing names for iov_iter direction initializers	2023-02-09 11:28:04 +01:00
vfs_dentry.c	…
vfs_dir.c	use less confusing names for iov_iter direction initializers	2023-02-09 11:28:04 +01:00
vfs_file.c	…
vfs_inode.c	…
vfs_inode_dotl.c	…
vfs_super.c	…
xattr.c	use less confusing names for iov_iter direction initializers	2023-02-09 11:28:04 +01:00
xattr.h	…