linux/fs/fscache
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
..
cache.c fscache: Use wrapper fscache_set_cache_state() directly when relinquishing 2022-04-08 23:54:37 +01:00
cookie.c fscache: add tracepoint when failing cookie 2022-08-09 14:13:59 +01:00
internal.h fscache: Move fscache_cookies_seq_ops specific code under CONFIG_PROC_FS 2022-04-08 23:54:37 +01:00
io.c use less confusing names for iov_iter direction initializers 2022-11-25 13:01:55 -05:00
Kconfig fscache: remove FSCACHE_OLD_API Kconfig option 2022-04-08 23:54:37 +01:00
main.c fscache: Implement cookie-level access helpers 2022-01-07 09:22:19 +00:00
Makefile fscache: Provide a means to begin an operation 2022-01-07 09:22:19 +00:00
proc.c fscache: Implement cookie registration 2022-01-07 09:22:19 +00:00
stats.c fscache, cachefiles: Display stat of culling events 2022-01-07 13:43:18 +00:00
volume.c fscache: Fix if condition in fscache_wait_on_volume_collision() 2022-07-05 16:12:20 +01:00