Omar Sandoval 6f67376318 direct_IO: use iov_iter_rw() instead of rw everywhere ... The rw parameter to direct_IO is redundant with iov_iter->type, and treated slightly differently just about everywhere it's used: some users do rw & WRITE, and others do rw == WRITE where they should be doing a bitwise check. Simplify this with the new iov_iter_rw() helper, which always returns either READ or WRITE. Signed-off-by: Omar Sandoval <osandov@osandov.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>		2015-04-11 22:29:45 -04:00
..
control.c	fuse: add __exit to fuse_ctl_cleanup	2014-04-28 14:19:21 +02:00
cuse.c	make new_sync_{read,write}() static	2015-04-11 22:29:40 -04:00
dev.c	fuse: use iov_iter_get_pages() for non-splice path	2015-04-11 22:29:41 -04:00
dir.c	VFS: (Scripted) Convert S_ISLNK/DIR/REG(dentry->d_inode) to d_is_*(dentry)	2015-02-22 11:38:41 -05:00
file.c	direct_IO: use iov_iter_rw() instead of rw everywhere	2015-04-11 22:29:45 -04:00
fuse_i.h	fuse: handle synchronous iocbs internally	2015-03-13 12:10:15 -04:00
inode.c	fs: remove mapping->backing_dev_info	2015-01-20 14:03:05 -07:00
Kconfig	fuse: Move CUSE Kconfig entry from fs/Kconfig into fs/fuse/Kconfig	2013-01-17 13:08:45 +01:00
Makefile	CUSE: implement CUSE - Character device in Userspace	2009-06-09 11:24:11 +02:00