From: Deepa Dinamani
Date: Mon, 7 Jan 2019 19:26:49 -0800
> The series introduces new socket timestamps that are
> y2038 safe.
Great discussion, but this is definitely net-next material and the net-next
tree is not open at this time.
On Tue, Jan 8, 2019 at 8:37 AM Willem de Bruijn
wrote:
>
> On Mon, Jan 7, 2019 at 10:29 PM Deepa Dinamani wrote:
> >
> > The series introduces new socket timestamps that are
> > y2038 safe.
> >
> > The time data types used for the existing socket timestamp
> > options: SO_TIMESTAMP, SO_TIMESTAMPN
On Mon, Jan 7, 2019 at 10:29 PM Deepa Dinamani wrote:
>
> The series introduces new socket timestamps that are
> y2038 safe.
>
> The time data types used for the existing socket timestamp
> options: SO_TIMESTAMP, SO_TIMESTAMPNS and SO_TIMESTAMPING
> are not y2038 safe. The series introduces SO_TIM
The series introduces new socket timestamps that are
y2038 safe.
The time data types used for the existing socket timestamp
options: SO_TIMESTAMP, SO_TIMESTAMPNS and SO_TIMESTAMPING
are not y2038 safe. The series introduces SO_TIMESTAMP_NEW,
SO_TIMESTAMPNS_NEW and SO_TIMESTAMPING_NEW to replace th