Hi Thomas,
On 06/09/2016:11:58:08 AM, Thomas Gleixner wrote:
> On Tue, 16 Aug 2016, Pratyush Anand wrote:
>
> That's a lot of churn to fix that simple problem. The two liner below
> should fix that as well, right?
Thanks a lot for your reply.
Yes, that should fix. I was n't sure if "setting
On Tue, 16 Aug 2016, Pratyush Anand wrote:
That's a lot of churn to fix that simple problem. The two liner below
should fix that as well, right?
Thanks,
tglx
diff --git a/drivers/rtc/rtc-cmos.c b/drivers/rtc/rtc-cmos.c
index 43745cac0141..cb8dfc3ee012 100644
---
On 08/30/16 at 04:38pm, Dave Young wrote:
> On 08/30/16 at 04:22pm, Dave Young wrote:
> > Hi, Pratyush
> >
> > On 08/16/16 at 08:55am, Pratyush Anand wrote:
> > > We have observed on few x86 machines with rtc-cmos device that
> > > hpet_rtc_interrupt() is called just after irq registration and
On 08/30/16 at 04:22pm, Dave Young wrote:
> Hi, Pratyush
>
> On 08/16/16 at 08:55am, Pratyush Anand wrote:
> > We have observed on few x86 machines with rtc-cmos device that
> > hpet_rtc_interrupt() is called just after irq registration and before
> > cmos_do_probe() could call
Hi, Pratyush
On 08/16/16 at 08:55am, Pratyush Anand wrote:
> We have observed on few x86 machines with rtc-cmos device that
> hpet_rtc_interrupt() is called just after irq registration and before
> cmos_do_probe() could call hpet_rtc_timer_init().
>
> So, neither hpet_default_delta nor
