David Miller wrote:
> From: Aya Mahfouz
> Date: Wed, 18 Nov 2015 08:36:44 +0200
>
> > Changes the definition of the pointer _expiry from time_t to
> > time64_t. This is to handle the Y2038 problem where time_t
> > will overflow in the year 2038. The change is safe because
> > the kernel subsyst
From: Arnd Bergmann
Date: Wed, 18 Nov 2015 22:08:54 +0100
> On Wednesday 18 November 2015 15:20:25 David Miller wrote:
>> From: Aya Mahfouz
>> Date: Wed, 18 Nov 2015 08:36:44 +0200
>>
>> > Changes the definition of the pointer _expiry from time_t to
>> > time64_t. This is to handle the Y2038 pr
On Wednesday 18 November 2015 15:20:25 David Miller wrote:
> From: Aya Mahfouz
> Date: Wed, 18 Nov 2015 08:36:44 +0200
>
> > Changes the definition of the pointer _expiry from time_t to
> > time64_t. This is to handle the Y2038 problem where time_t
> > will overflow in the year 2038. The change i
From: Aya Mahfouz
Date: Wed, 18 Nov 2015 08:36:44 +0200
> Changes the definition of the pointer _expiry from time_t to
> time64_t. This is to handle the Y2038 problem where time_t
> will overflow in the year 2038. The change is safe because
> the kernel subsystems that call dns_query pass NULL.
>
Changes the definition of the pointer _expiry from time_t to
time64_t. This is to handle the Y2038 problem where time_t
will overflow in the year 2038. The change is safe because
the kernel subsystems that call dns_query pass NULL.
Signed-off-by: Arnd Bergmann
Signed-off-by: Aya Mahfouz
---
Chan