Re: [PATCH v2 0/3] rtc: make st-lpc robust against y2038/2106 bug

2017-07-09 Thread Alexandre Belloni
On 19/06/2017 at 11:36:19 +0200, Benjamin Gaignard wrote: > On 32bits platforms "struct timeval" or "time_t" are using u32 to code the > date, this cause tools like "date" or "hwclock" failed even before setting > the RTC device if the date is superior to year 2038 (or 2106). > > To avoid this pro

Re: [PATCH v2 0/3] rtc: make st-lpc robust against y2038/2106 bug

2017-07-04 Thread Benjamin Gaignard
2017-06-24 0:34 GMT+02:00 Shuah Khan : > Hi Alexandre, > > On 06/23/2017 04:09 PM, Alexandre Belloni wrote: >> On 23/06/2017 at 13:40:41 -0600, Shuah Khan wrote: >>> On 06/19/2017 03:36 AM, Benjamin Gaignard wrote: On 32bits platforms "struct timeval" or "time_t" are using u32 to code the

Re: [PATCH v2 0/3] rtc: make st-lpc robust against y2038/2106 bug

2017-06-23 Thread Shuah Khan
Hi Alexandre, On 06/23/2017 04:09 PM, Alexandre Belloni wrote: > On 23/06/2017 at 13:40:41 -0600, Shuah Khan wrote: >> On 06/19/2017 03:36 AM, Benjamin Gaignard wrote: >>> On 32bits platforms "struct timeval" or "time_t" are using u32 to code the >>> date, this cause tools like "date" or "hwclock"

Re: [PATCH v2 0/3] rtc: make st-lpc robust against y2038/2106 bug

2017-06-23 Thread Alexandre Belloni
On 23/06/2017 at 13:40:41 -0600, Shuah Khan wrote: > On 06/19/2017 03:36 AM, Benjamin Gaignard wrote: > > On 32bits platforms "struct timeval" or "time_t" are using u32 to code the > > date, this cause tools like "date" or "hwclock" failed even before setting > > the RTC device if the date is super

Re: [PATCH v2 0/3] rtc: make st-lpc robust against y2038/2106 bug

2017-06-23 Thread Shuah Khan
On 06/19/2017 03:36 AM, Benjamin Gaignard wrote: > On 32bits platforms "struct timeval" or "time_t" are using u32 to code the > date, this cause tools like "date" or "hwclock" failed even before setting > the RTC device if the date is superior to year 2038 (or 2106). > > To avoid this problem I ad