On 05/01/2014 01:44 AM, Mel Gorman wrote: > X86 prefers the use of unsigned types for iterators and there is a > tendency to mix whether a signed or unsigned type if used for page > order. This converts a number of sites in mm/page_alloc.c to use > unsigned int for order where possible. Does this actually generate any different code? I'd actually expect something like 'order' to be one of the easiest things for the compiler to figure out an absolute range on. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
