From: Herbert Xu <herbert@gondor.apana.org.au> Date: Sat, 31 May 2003 19:42:30 +1000
Here is a trivial patch to replace the one occurance u64 with __u64
in linux/xfrm.h.
Applied, thanks.
Why?
As is evident from (a) include/linux standard policy and (b) patches applied to CryptoAPI in the past, we should be using kernel standard types: u64, not __u64.
One among many practical reasons is the __foo<size> is gcc-specific, and not guaranteed in other compilers. Use of standard kernel types allows for the best compiler-specific type to be chosen (probably u_int<size>_t if not __u<size>)
Jeff
- : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html