Joe Perches wrote: > On Thu, 2008-03-06 at 10:07 -0800, Kok, Auke wrote: >> (which, BTW also could use the uint32_t -> u32 (etc) changes... while you're at it) > > I think this does what you want: > > for size in "8" "16" "32" "64" ; do \ > sed -r -i -e 's/\bu_{0,1}int'$size'_t\b/u'$size'/g' \ > $(grep -rPlw --include=*.[ch] 'u_{0,1}int'$size'_t' drivers/net/e1000 drivers/net/ixgb); done > > But why? boolean_t is used by 3 subsystems with local typedefs. > These others are much more frequently used by kernel source. > > $ grep -rPlw --include=*.[ch] "u{0,1}_{0,1}int(8|16|32|64)_t" * | wc -l > 876 > > include/linux/types.h has typedefs for these but not boolean_t > > include/linux/types.h:typedef __u8 u_int8_t; > include/linux/types.h:typedef __s8 int8_t; > include/linux/types.h:typedef __u16 u_int16_t; > include/linux/types.h:typedef __s16 int16_t; > include/linux/types.h:typedef __u32 u_int32_t; > include/linux/types.h:typedef __s32 int32_t; > include/linux/types.h:typedef __u8 uint8_t; > include/linux/types.h:typedef __u16 uint16_t; > include/linux/types.h:typedef __u32 uint32_t; > include/linux/types.h:typedef __u64 uint64_t; > include/linux/types.h:typedef __u64 u_int64_t; > include/linux/types.h:typedef __s64 int64_t; > Why not the other way around ? inttypes.h is C99 and defines int16_t (or uint16_t). i do not see any reason not to use them or any other type (like __u8) that does actually the same. In that case we do not need different type names for userspace/kernelspace, or is there an other name for int ? in that case we can remove the whole heap of typedef's. re, wh -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html