On Tue, 13 May 2014, Christoph Hellwig wrote: > On Tue, May 13, 2014 at 05:33:01PM +0200, Thomas Gleixner wrote: > > Err, we CANNOT do that. We cannot move ANY 32 bit architecture to > > 64bit time_t without breaking the world and some more. > > Of course we can, we just need to still provide the existing 32-bit > time_t ABIs for backwards compatiblity. That's how we handled > extensions of other types like off_t in the past. Sorry, misunderstood you there. Sure, I agree that we need to fix it anyway plus all timespec/timeval usage sites. It's on my and John Stultz radar as well. Just the sheer amount of syscalls, ioctls etc. makes one shudder. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
