>From fe2cc53ee013a4d4d0317d418e7019fe6533a5a8
Alarm delivery could be noticably late in the !CONFIG_NOHZ case because lost
ticks weren't being taken into account. This is now treated more carefully,
with the time between ticks being calculated and the appropriate number of
ticks delivered to the
>From a113552a171e5a30a8a478f7d4dcf8d0ff08f12f Mon Sep 17 00:00:00 2001
Alarm delivery could be noticably late in the !CONFIG_NOHZ case because lost
ticks weren't being taken into account. This is now treated more carefully,
with the time between ticks being calculated and the appropriate number
