diff options
author | Christoph Hellwig <hch@lst.de> | 2016-11-01 07:40:11 -0600 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2016-11-01 09:43:26 -0600 |
commit | d38499530e5f170d30f32d3841fade204e63081d (patch) | |
tree | 931cc16c86ab8d7b07dcda66febb6b1af21e2234 /include/linux/uio.h | |
parent | 70fd76140a6cb63262bd47b68d57b42e889c10ee (diff) | |
download | op-kernel-dev-d38499530e5f170d30f32d3841fade204e63081d.zip op-kernel-dev-d38499530e5f170d30f32d3841fade204e63081d.tar.gz |
fs: decouple READ and WRITE from the block layer ops
Move READ and WRITE to kernel.h and don't define them in terms of block
layer ops; they are our generic data direction indicators these days
and have no more resemblance with the block layer ops.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'include/linux/uio.h')
-rw-r--r-- | include/linux/uio.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/uio.h b/include/linux/uio.h index 6e22b54..d5aba15 100644 --- a/include/linux/uio.h +++ b/include/linux/uio.h @@ -125,7 +125,7 @@ static inline bool iter_is_iovec(const struct iov_iter *i) * * The ?: is just for type safety. */ -#define iov_iter_rw(i) ((0 ? (struct iov_iter *)0 : (i))->type & RW_MASK) +#define iov_iter_rw(i) ((0 ? (struct iov_iter *)0 : (i))->type & (READ | WRITE)) /* * Cap the iov_iter by given limit; note that the second argument is |