On Oct 2 2007 19:57, Jan Engelhardt wrote: >>> And u_int8_t. Better is uint32_t[8], because that is what the linux >>> bitops work with. (And, unfortunately, it's buggy so we end up >>> continuing to use own macros.) >> >> But with uint32_t you have to remember about big/low-endianism & network/host >> byte order conversion and stuff. Not sure if that's really better. > >Should not matter. The endianess does not change between user- and >kernelspace, unless type widths do. Should have read: [...]kernelspace, unlike type widths, which do. - To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
