Wed, Apr 01, 2015 at 10:02:14PM +0200, Sven Eckelmann wrote:
The linux/if_ether.h -> netinet/if_ether.h seems to be understandable (but rather unfortunate).
I am not sure why why you include linux/types.h to the different source files. Most likely because this include should actually be in packet.h as mentioned in https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2015-March/012930.html https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2015-March/012942.html
I assume any changes in packet.h must be done in batman-adv first, then ported to batctl, and preferably not the other way around. And since I was only concerned with batctl, I saw packet.h as read-only.
Moving linux/types.h to packet.h does make sense I think. However, it also brings linux/if_ether.h there, which immediately makes musl support difficult. Maybe even impractical.
I'm not saying that's wrong, because I'm not trying to say batctl needs musl support in the first place. Just another point to consider.