Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()

2015-03-24 Thread John Stultz
On Thu, Mar 19, 2015 at 4:29 PM, Alessandro Zummo wrote: > On Wed, 18 Mar 2015 10:37:26 -0700 > John Stultz wrote: > >> On Wed, Jan 28, 2015 at 10:27 AM, Alessandro Zummo >> wrote: >> > On Thu, 29 Jan 2015 00:12:09 +0800 >> > Xunlei Pang wrote: >> > >> >> ping Alessandro >> > >> > -EBUSY . s

Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()

2015-03-19 Thread Alessandro Zummo
On Wed, 18 Mar 2015 10:37:26 -0700 John Stultz wrote: > On Wed, Jan 28, 2015 at 10:27 AM, Alessandro Zummo > wrote: > > On Thu, 29 Jan 2015 00:12:09 +0800 > > Xunlei Pang wrote: > > > >> ping Alessandro > > > > -EBUSY . saw that, looks fine anyhow, but would like to > > have a deeper look.

Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()

2015-03-18 Thread Alessandro Zummo
On Wed, 18 Mar 2015 10:37:26 -0700 John Stultz wrote: > Hey Alessandro, > I was hoping to let these go through you (with your review), but if > you're still too busy I can queue them if you'd rather. Hello, will review today and let you know. -- Best regards, Alessandro Zummo, Tow

Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()

2015-03-18 Thread John Stultz
On Wed, Jan 28, 2015 at 10:27 AM, Alessandro Zummo wrote: > On Thu, 29 Jan 2015 00:12:09 +0800 > Xunlei Pang wrote: > >> ping Alessandro > > -EBUSY . saw that, looks fine anyhow, but would like to > have a deeper look. we have still some time 'till 2038, right? ;) Hey Alessandro, I was hopi

Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()

2015-01-28 Thread Xunlei Pang
ping Alessandro On 21 January 2015 at 00:21, Xunlei Pang wrote: > This patch series relies on a former patchset[1], it provides y2038/y2106 > safe rtc_class_ops.set_mmss64(), and converts some possible users of > set_mmss() > to use set_mmss64(), in the hope that making these users(i.e. rtc driv

Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()

2015-01-28 Thread Alessandro Zummo
On Thu, 29 Jan 2015 00:12:09 +0800 Xunlei Pang wrote: > ping Alessandro -EBUSY . saw that, looks fine anyhow, but would like to have a deeper look. we have still some time 'till 2038, right? ;) -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towerte

Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()

2015-01-28 Thread John Stultz
On Wed, Jan 28, 2015 at 10:27 AM, Alessandro Zummo wrote: > On Thu, 29 Jan 2015 00:12:09 +0800 > Xunlei Pang wrote: > >> ping Alessandro > > -EBUSY . saw that, looks fine anyhow, but would like to > have a deeper look. we have still some time 'till 2038, right? ;) While that is true, for folk

[RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()

2015-01-20 Thread Xunlei Pang
This patch series relies on a former patchset[1], it provides y2038/y2106 safe rtc_class_ops.set_mmss64(), and converts some possible users of set_mmss() to use set_mmss64(), in the hope that making these users(i.e. rtc drivers) y2038/y2106 safe. [1] https://lkml.org/lkml/2014/11/18/218 [2] v1: ht