> This is not merge fallout, but has been this way since the driver was > merged the first time. Hm ok I thought it might have been a "static inline" in the header file and gotten split up with the driver split. > I do not know why it was done this way and I am > not familiar enough with gcc optimization to know the implications of > this (or what the better way should be). What do you suggest? Well I think simply removing the inline will cause the compiler to do the exact same thing as it does now and look less strange. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part