> Ahem... So what does > x |= y; > turns into with that approach?
BTW, you can simply typedef __be16 ubi16_t; etc. and define conversion functions as cpu_to_ubi16(x) being (__force ubi16_t)cpu_to_be16(x), etc. sparse will do all checks just fine, you still have bitwise operations (might or might be not relevant in your case) and for gcc it simply becomes __be16, etc - i.e. an integer type. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
