On 07-10-15, 12:07, Greg Kroah-Hartman wrote: > Why would you be wanting to create a "unsigned long" as an api anyway? > Just force it to be u64 all the time, can't you do that?
Okay, so the variable in question (lets say frequency) is an 'unsigned long' and that's how all the APIs of clock framework expect/define it. And you are probably saying that we do this: unsigned long freq; debugfs_create_u64((u64 *)&freq); Right? Or are you asking to update clock APIs to be converted to u64? This will break things on a 32 bit architecture where unsigned long is 32 bits long, as doing this will overwrite the next 32 bits: *freq = XYZ; -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
