Florian Bezdeka writes:
> On 05.05.21 18:53, Jan Kiszka via Xenomai wrote:
>> From: Philippe Gerum
>>
>> As internal interfaces are gradually being made y2038-safe, the
>> timespec64 type should be used internally by the kernel to represent
>> time values. Apply the same reasoning to Cobalt.
On 05.05.21 18:53, Jan Kiszka via Xenomai wrote:
> From: Philippe Gerum
>
> As internal interfaces are gradually being made y2038-safe, the
> timespec64 type should be used internally by the kernel to represent
> time values. Apply the same reasoning to Cobalt.
>
> We still use a legacy
From: Philippe Gerum
As internal interfaces are gradually being made y2038-safe, the
timespec64 type should be used internally by the kernel to represent
time values. Apply the same reasoning to Cobalt.
We still use a legacy y2038-unsafe timespec type at the kernel<->user
interface boundary
