diff mbox

[RFC,v3,1/5] new helper: iov_iter_rw()

Message ID d80b0e1347c7df986754cedbf35abbc441affc59.1426626029.git.osandov@osandov.com (mailing list archive)
State New, archived
Headers show

Commit Message

Omar Sandoval March 17, 2015, 9:04 p.m. UTC
Get either READ or WRITE out of iter->type.

Signed-off-by: Omar Sandoval <osandov@osandov.com>
---
Ok, let's do that, then.

 include/linux/uio.h | 8 ++++++++
 1 file changed, 8 insertions(+)

Comments

David Sterba March 18, 2015, 1:42 p.m. UTC | #1
On Tue, Mar 17, 2015 at 02:04:02PM -0700, Omar Sandoval wrote:
>  /*
> + * 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)

I'm fine with that, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

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