Al Viro de4eda9de2 use less confusing names for iov_iter direction initializers ... 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>		2022-11-25 13:01:55 -05:00
..
iotlb.c	vhost_iotlb: split out IOTLB initialization	2022-05-31 12:44:28 -04:00
Kconfig	vhost_vdpa: implement IRQ offloading in vhost_vdpa	2020-08-05 11:08:42 -04:00
Makefile	vhost: introduce vDPA-based backend	2020-04-02 10:41:40 -04:00
net.c	use less confusing names for iov_iter direction initializers	2022-11-25 13:01:55 -05:00
scsi.c	use less confusing names for iov_iter direction initializers	2022-11-25 13:01:55 -05:00
test.c	vhost: rename vhost_work_dev_flush	2022-05-31 12:45:10 -04:00
test.h	tools/virtio: Add --reset	2020-06-22 12:34:21 -04:00
vdpa.c	vhost-vdpa: uAPI to suspend the device	2022-08-11 04:31:15 -04:00
vhost.c	use less confusing names for iov_iter direction initializers	2022-11-25 13:01:55 -05:00
vhost.h	vhost: rename vhost_work_dev_flush	2022-05-31 12:45:10 -04:00
vringh.c	use less confusing names for iov_iter direction initializers	2022-11-25 13:01:55 -05:00
vsock.c	use less confusing names for iov_iter direction initializers	2022-11-25 13:01:55 -05:00