Hi Slawek,
On Fri, Jan 13, 2012, Slawomir Bochenski wrote:
> + union {
> + uint32_t val32u;
> + uint16_t val16u;
> + uint8_t val8u;
> + char *valstr;
> + };
To keep consistent with some other places in BlueZ code, could you do
this as:
union {
uint32_t u32;
uint16_t u16;
uint8_t u8;
char *str;
} val;
After which you'd access these as entry->val.u32, etc.
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
