On Mon, Mar 16, 2015 at 05:36:05PM +0000, Al Viro wrote:
> On Mon, Mar 16, 2015 at 04:33:49AM -0700, Omar Sandoval wrote:
> > Get either READ or WRITE out of iter->type.
>
> Umm...
>
> > + * Get one of READ or WRITE out of iter->type without any other flags OR'd
> > in
> > + * with it.
> > + */
> > +static inline int iov_iter_rw(const struct iov_iter *i)
> > +{
> > + return i->type & RW_MASK;
> > +}
>
> TBH, I would turn that into a macro. Reason: indirect includes.
Agreed, but the proposed define is rather cryptic and I was not able to
understand the meaning on the first glance.
> #define iov_iter_rw(i) ((0 ? (struct iov_iter *)0 : (i))->type & RW_MASK)
This worked for me, does not compile with anything else than
'struct iov_iter*' as i:
#define iov_iter_rw(i) ({ \
struct iov_iter __iter = *(i); \
(i)->type & RW_MASK; \
})
The assignment is optimized out.
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
