* [PATCH] clockevents: fix bogus next_event reset for oneshot broadcast devices
@ 2007-09-27 22:17 Thomas Gleixner
0 siblings, 0 replies; only message in thread
From: Thomas Gleixner @ 2007-09-27 22:17 UTC (permalink / raw)
To: LKML; +Cc: Andrew Morton, Ralf Baechle
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@linutronix.de>
Acked-and-tested-by: Ralf Baechle <ralf@linux-mips.org>
---
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;
-
tick_do_periodic_broadcast();
/*
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-09-27 22:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-09-27 22:17 [PATCH] clockevents: fix bogus next_event reset for oneshot broadcast devices Thomas Gleixner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®