Hi Herbert, I have a crypto offload driver that has macro's defined as below. They are autogenerated by hardware tool. Some of them are quite long - even longer than below example. Would they be a problem in accepting into the Linux driver tree. They are formed by concat register name with bit field definition defined by the hardware tool. Sample: ======= #define IPE_TKN_CTRL_ADDR 0x100 #define F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_LSB 0 #define F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_MSB 1 #define F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_WIDTH 2 #define F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_MASK 0x3 #define F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_SHIFT_MASK 0x0 #define F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_READ(data) \ (F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_MASK & (unsigned int)(data)) #define F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_WRITE(data) \ (F_IPE_TKN_CTRL_STAT_ACTIVE_TOKENS_MASK & (unsigned int)(data)) -Loc -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
