On 19/05/15 07:08, Tina Ruchandani wrote:
struct timeval uses a 32-bit field for representing seconds,
which will overflow in the year 2038 and beyond. This patch replaces
struct timeval with 64-bit ktime_t which is 2038 safe.
The patch is part of a larger effort to remove instances of
32-bit
On Wed, May 20, 2015 at 08:16:24AM -0500, Bjorn Helgaas wrote:
On Tue, May 19, 2015 at 1:08 AM, Tina Ruchandani
ruchandani.t...@gmail.com wrote:
struct timeval uses a 32-bit field for representing seconds,
which will overflow in the year 2038 and beyond. This patch replaces
struct timeval
On Tue, May 19, 2015 at 1:08 AM, Tina Ruchandani
ruchandani.t...@gmail.com wrote:
struct timeval uses a 32-bit field for representing seconds,
which will overflow in the year 2038 and beyond. This patch replaces
struct timeval with 64-bit ktime_t which is 2038 safe.
The patch is part of a
struct timeval uses a 32-bit field for representing seconds,
which will overflow in the year 2038 and beyond. This patch replaces
struct timeval with 64-bit ktime_t which is 2038 safe.
The patch is part of a larger effort to remove instances of
32-bit timekeeping variables (timeval, time_t and
On 05/19/2015 02:08 AM, Tina Ruchandani wrote:
struct timeval uses a 32-bit field for representing seconds,
which will overflow in the year 2038 and beyond. This patch replaces
struct timeval with 64-bit ktime_t which is 2038 safe.
The patch is part of a larger effort to remove instances of
