commit | de4eda9de2d957ef2d6a8365a01e26a435e958cb | [log] [tgz] |
---|---|---|
author | Al Viro <viro@zeniv.linux.org.uk> | Thu Sep 15 20:25:47 2022 -0400 |
committer | Al Viro <viro@zeniv.linux.org.uk> | Fri Nov 25 13:01:55 2022 -0500 |
tree | 49b0d60dedb65af7f0d3e874ee9c661e6b09697b | |
parent | a41dad905e5a388f88435a517de102e9b2c8e43d [diff] |
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>