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
Makefile
stub.h
stub_dev.c	usb: usbip: fix a refcount leak in stub_probe()	2022-04-21 19:01:22 +02:00
stub_main.c	usb: move from strlcpy with unused retval to strscpy	2022-08-19 11:08:54 +02:00
stub_rx.c	usbip: add USBIP_URB_* URB transfer flags	2022-08-31 09:07:53 +02:00
stub_tx.c
usbip_common.c	use less confusing names for iov_iter direction initializers	2022-11-25 13:01:55 -05:00
usbip_common.h
usbip_event.c
vhci.h
vhci_hcd.c
vhci_rx.c
vhci_sysfs.c
vhci_tx.c
vudc.h
vudc_dev.c
vudc_main.c	usb: usbip: eliminate anonymous module_init & module_exit	2022-03-18 12:52:56 +01:00
vudc_rx.c	USB: usbip: clean up mixed use of _irq() and _irqsave()	2022-06-10 11:48:15 +02:00
vudc_sysfs.c	usbip: vudc: Don't enable IRQs prematurely	2022-06-10 11:48:19 +02:00
vudc_transfer.c
vudc_tx.c