Re: [RFC PATCH 1/4] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t

2014-11-28 Thread pang.xunlei
On 28 November 2014 at 07:47, Arnd Bergmann wrote: > On Friday 28 November 2014 00:02:47 Thomas Gleixner wrote: >> >> > static int rtc_update_alarm(struct device *dev, struct rtc_time *alrm) >> > { >> > struct rtc_time alarm_tm, now_tm; >> > - unsigned long now, time; >> > +

Re: [RFC PATCH 1/4] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t

2014-11-28 Thread pang.xunlei
On 28 November 2014 at 07:47, Arnd Bergmann a...@arndb.de wrote: On Friday 28 November 2014 00:02:47 Thomas Gleixner wrote: static int rtc_update_alarm(struct device *dev, struct rtc_time *alrm) { struct rtc_time alarm_tm, now_tm; - unsigned long now, time; + time64_t

Re: [RFC PATCH 1/4] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t

2014-11-27 Thread Arnd Bergmann
On Friday 28 November 2014 00:02:47 Thomas Gleixner wrote: > > > static int rtc_update_alarm(struct device *dev, struct rtc_time *alrm) > > { > > struct rtc_time alarm_tm, now_tm; > > - unsigned long now, time; > > + time64_t now, time; > > struct platform_device *pdev =

Re: [RFC PATCH 1/4] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t

2014-11-27 Thread Thomas Gleixner
On Thu, 27 Nov 2014, Xunlei Pang wrote: > We want to convert y2038 unsafe rtc_class_ops.set_mmss() and all its > users to use time64_t. mxc_rtc_set_mmss() in "mxc" driver is one of > its users, but it uses get_alarm_or_time()/set_alarm_or_time() internal > interfaces which are also y2038 unsafe. >

[RFC PATCH 1/4] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t

2014-11-27 Thread Xunlei Pang
We want to convert y2038 unsafe rtc_class_ops.set_mmss() and all its users to use time64_t. mxc_rtc_set_mmss() in "mxc" driver is one of its users, but it uses get_alarm_or_time()/set_alarm_or_time() internal interfaces which are also y2038 unsafe. So here as a separate patch, it converts these

[RFC PATCH 1/4] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t

2014-11-27 Thread Xunlei Pang
We want to convert y2038 unsafe rtc_class_ops.set_mmss() and all its users to use time64_t. mxc_rtc_set_mmss() in mxc driver is one of its users, but it uses get_alarm_or_time()/set_alarm_or_time() internal interfaces which are also y2038 unsafe. So here as a separate patch, it converts these two

Re: [RFC PATCH 1/4] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t

2014-11-27 Thread Thomas Gleixner
On Thu, 27 Nov 2014, Xunlei Pang wrote: We want to convert y2038 unsafe rtc_class_ops.set_mmss() and all its users to use time64_t. mxc_rtc_set_mmss() in mxc driver is one of its users, but it uses get_alarm_or_time()/set_alarm_or_time() internal interfaces which are also y2038 unsafe. So

Re: [RFC PATCH 1/4] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t

2014-11-27 Thread Arnd Bergmann
On Friday 28 November 2014 00:02:47 Thomas Gleixner wrote: static int rtc_update_alarm(struct device *dev, struct rtc_time *alrm) { struct rtc_time alarm_tm, now_tm; - unsigned long now, time; + time64_t now, time; struct platform_device *pdev =