On Thu, Jan 25, 2018 at 10:12:25AM +0100, Miroslav Lichvar wrote: > Do I understand it correctly that no other interface is using > nanoseconds since 1970? We probably don't have to worry about year > 2262 yet, but wouldn't it be better to make it consistent with the > timestamping API using timespec? Or is it just better to avoid the > 64/32-bit mess of time_t?
I prefer a single 64 bit nanoseconds field: - Applications won't have to convert to timespec. - Avoids the time_t issue. Thanks, Richard
