[rtc-linux] Fwd: Hot List Of R2Technologies

2017-06-21 Thread raju bakrewar
Hi Friends, Greetings for the day, Please find the list of skilled R2Technologies LLC consultants who are actively looking for new role and please share your requirements to ra...@r2techcorp.com S.No CANDIDATE SKILL SET EXPERIENCE LOCATION RELOCATION 1 Syed .Net Developer 8+ Plano,TX YES 2 Su

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Pavel Machek
Hi! > > > Or not, having an RTC set in the past is actually quite common. I'd find > > > it weird to have a new device boot and be set to a date in the future. > > > > ...but still better than board stuck in the past, no? > > > > > Also note that the threshold or offset thing may seem like a goo

[rtc-linux] Re: [PATCH 35/51] rtc: pm8xxx: stop using rtc deprecated functions

2017-06-21 Thread kbuild test robot
-functions/20170621-044455 base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make ARCH=i386 All

[rtc-linux] Fwd: Hot List Of R2Technologies

2017-06-21 Thread raju bakrewar
Hi Friends, Greetings for the day, Please find the list of skilled R2Technologies LLC consultants who are actively looking for new role and please share your requirements to ra...@r2techcorp.com S.No CANDIDATE SKILL SET EXPERIENCE LOCATION RELOCATION 1 Syed .Net Developer 8+ Plano,TX YES 2 Su

[rtc-linux] Hot List Of R2Technologies

2017-06-21 Thread raju bakrewar
Hi Friends, Greetings for the day, Please find the list of skilled R2Technologies consultants who are actively looking for new role and please share your requirements to ra...@r2techcorp.com *CANDIDATE* *SKILL SET* *EXPERIENCE * *LOCATION* *RELOCATION* *VISA* *Syed* *.Net Developer* *8+* *Plano,T

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Alexandre Belloni
On 21/06/2017 at 08:34:43 +0200, Pavel Machek wrote: > Hi! > > > > > > I think tglx had a plan for offsetting the time at some point so > > > > > 32-bit > > > > > platform can pass 2038 properly. > > > > > > > > Yes, but there are still quite some issues to solve there: > > > > > > > > 1)

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Pavel Machek
Hi! > > > > I think tglx had a plan for offsetting the time at some point so 32-bit > > > > platform can pass 2038 properly. > > > > > > Yes, but there are still quite some issues to solve there: > > > > > > 1) How do you tell the system that it should apply the offset in the > > >

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Alexandre Belloni
On 21/06/2017 at 10:19:49 +0100, Russell King - ARM Linux wrote: > On Wed, Jun 21, 2017 at 10:39:07AM +0200, Alexandre Belloni wrote: > > On 21/06/2017 at 09:51:52 +0200, Pavel Machek wrote: > > > If someone uses different threshold, well, there will be > > > confusion. But only for users that have

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Russell King - ARM Linux
On Wed, Jun 21, 2017 at 09:26:51AM +, David Laight wrote: > From: Russell King - ARM Linux > > Sent: 20 June 2017 22:16 > .. > > Consider that at the moment, we define the 32-bit RTC representation to > > start at a well known epoch. We _could_ decide that when it wraps to > > 0x8000 secon

[rtc-linux] RE: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread David Laight
From: Russell King - ARM Linux > Sent: 20 June 2017 22:16 .. > Consider that at the moment, we define the 32-bit RTC representation to > start at a well known epoch. We _could_ decide that when it wraps to > 0x8000 seconds, we'll define the lower 0x4000 seconds to mean > dates in the futur

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Russell King - ARM Linux
On Wed, Jun 21, 2017 at 10:39:07AM +0200, Alexandre Belloni wrote: > On 21/06/2017 at 09:51:52 +0200, Pavel Machek wrote: > > If someone uses different threshold, well, there will be > > confusion. But only for users that have their rtc set to the past, > > which is quite unusual. > > > > Or not,

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Benjamin Gaignard
2017-06-21 0:08 GMT+02:00 Pavel Machek : > Hi! > >> >> > This is it. >> >> > https://patchwork.kernel.org/patch/6219401/ >> >> >> >> Thanks. >> >> >> >> Yes, that's argument against changing rtc _drivers_ for hardware that >> >> can not do better than 32bit. For generic code (such as 44/51 sysfs, >

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Alexandre Belloni
On 21/06/2017 at 09:51:52 +0200, Pavel Machek wrote: > Hi! > > > > I agree with that but not the android guys. They seem to mandate an RTC > > > that can store time from 01/01/1970. I don't know much more than that > > > because they never cared to explain why that was actually necessary > > > (ap

[rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

2017-06-21 Thread Pavel Machek
Hi! > > I agree with that but not the android guys. They seem to mandate an RTC > > that can store time from 01/01/1970. I don't know much more than that > > because they never cared to explain why that was actually necessary > > (apart from a laconic "this will result in a bad user experience") >