Very interesting. We were wondering why the latest git tree doesn't show tons of endianness warnings, but it appears that when sparse finds these dubious bitfields it turns off all other warnings. Zhu Yi, can you apply this patch to your tree and review your code and the sparse output and stick le16_to_cpu()/le32_to_cpu() into the appropriate places? A whole bunch of things there are endianness broken and sparse probably only gives you an approximation of what errors there are. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
