[PATCH] clockevents: fix bogus next_event reset for oneshotbroadcast devices

From: Thomas Gleixner
Date: Thu Sep 27 2007 - 18:17:21 EST

In periodic broadcast mode the next_event member of the broadcast device
structure is set to KTIME_MAX in the interrupt handler. This is wrong,
as we calculate the next periodic interrupt with this variable.

Remove it.

Noticed by Ralf. MIPS is the first user of this mode, it does not affect
existing users.

Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Acked-and-tested-by: Ralf Baechle <ralf@xxxxxxxxxxxxxx>

diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
index 0962e05..acf15b4 100644
--- a/kernel/time/tick-broadcast.c
+++ b/kernel/time/tick-broadcast.c
@@ -176,8 +176,6 @@ static void tick_do_periodic_broadcast(void)
static void tick_handle_periodic_broadcast(struct clock_event_device *dev)
- dev->next_event.tv64 = KTIME_MAX;


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/