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
..
Kconfig	VMCI: Add support for ARM64	2022-04-24 17:32:14 +02:00
Makefile
vmci_context.c	misc: vmw_vmci: replace usage of found with dedicated list iterator variable	2022-04-24 17:24:09 +02:00
vmci_context.h
vmci_datagram.c
vmci_datagram.h
vmci_doorbell.c
vmci_doorbell.h
vmci_driver.c
vmci_driver.h
vmci_event.c	misc: vmw_vmci: Switch to kvfree_rcu() API	2021-12-21 10:25:15 +01:00
vmci_event.h
vmci_guest.c	VMCI: Add support for ARM64	2022-04-24 17:32:14 +02:00
vmci_handle_array.c
vmci_handle_array.h
vmci_host.c
vmci_queue_pair.c	use less confusing names for iov_iter direction initializers	2022-11-25 13:01:55 -05:00
vmci_queue_pair.h
vmci_resource.c
vmci_resource.h
vmci_route.c
vmci_route.h