[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <d80b0e1347c7df986754cedbf35abbc441affc59.1426626029.git.osandov@osandov.com>
Date: Tue, 17 Mar 2015 14:04:02 -0700
From: Omar Sandoval <osandov@...ndov.com>
To: Al Viro <viro@...IV.linux.org.uk>, David Sterba <dsterba@...e.cz>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Omar Sandoval <osandov@...ndov.com>
Subject: [RFC PATCH v3 1/5] new helper: iov_iter_rw()
Get either READ or WRITE out of iter->type.
Signed-off-by: Omar Sandoval <osandov@...ndov.com>
---
Ok, let's do that, then.
include/linux/uio.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/include/linux/uio.h b/include/linux/uio.h
index 7188029..71889c9 100644
--- a/include/linux/uio.h
+++ b/include/linux/uio.h
@@ -111,6 +111,14 @@ static inline bool iter_is_iovec(struct iov_iter *i)
}
/*
+ * Get one of READ or WRITE out of iter->type without any other flags OR'd in
+ * with it.
+ *
+ * The ?: is just for type safety.
+ */
+#define iov_iter_rw(i) ((0 ? (struct iov_iter *)0 : (i))->type & RW_MASK)
+
+/*
* Cap the iov_iter by given limit; note that the second argument is
* *not* the new size - it's upper limit for such. Passing it a value
* greater than the amount of data in iov_iter is fine - it'll just do
--
2.3.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists