On Fri, Jan 23, 2009 at 09:52:44AM -0500, Vlad Yasevich wrote: > > I'll give it some thought. It would clean up all the __force > casts, but it will be a little misleading to define a packet > checksum as little endian. :) Not at all! Just because something is on the network doesn't mean that it's big-endian. In this case, we're using the little- endian CRC32C implementation for the checksum so it makes perfect sense for it to be marked as __le32. Network-order just has to be fixed in endian, i.e., either big or small, you just need to stick with the one you choose regardless of the endianness of the host. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
