On Fri, 2 Mar 2018 12:26:03 +0100 (CET)
Thomas Gleixner wrote:
> On Fri, 2 Mar 2018, Sebastian Andrzej Siewior wrote:
>
> > I've been looking at this in v3.10-RT where it got in. The patch
> > description says
> >
> > |The ntp code for notify_cmos_timer() is called from a
On Fri, 2 Mar 2018 12:26:03 +0100 (CET)
Thomas Gleixner wrote:
> On Fri, 2 Mar 2018, Sebastian Andrzej Siewior wrote:
>
> > I've been looking at this in v3.10-RT where it got in. The patch
> > description says
> >
> > |The ntp code for notify_cmos_timer() is called from a hard interrupt
> >
On Fri, 2 Mar 2018, Sebastian Andrzej Siewior wrote:
> I've been looking at this in v3.10-RT where it got in. The patch
> description says
>
> |The ntp code for notify_cmos_timer() is called from a hard interrupt
> |context.
>
> I see only one caller of ntp_notify_cmos_timer() and that is
>
On Fri, 2 Mar 2018, Sebastian Andrzej Siewior wrote:
> I've been looking at this in v3.10-RT where it got in. The patch
> description says
>
> |The ntp code for notify_cmos_timer() is called from a hard interrupt
> |context.
>
> I see only one caller of ntp_notify_cmos_timer() and that is
>
I've been looking at this in v3.10-RT where it got in. The patch
description says
|The ntp code for notify_cmos_timer() is called from a hard interrupt
|context.
I see only one caller of ntp_notify_cmos_timer() and that is
do_adjtimex() after "raw_spin_unlock_irqrestore()".
I see a few callers
I've been looking at this in v3.10-RT where it got in. The patch
description says
|The ntp code for notify_cmos_timer() is called from a hard interrupt
|context.
I see only one caller of ntp_notify_cmos_timer() and that is
do_adjtimex() after "raw_spin_unlock_irqrestore()".
I see a few callers
6 matches
Mail list logo