Commit:     c8a1d398de70a7774359b4720c392891cdd485f9
Parent:     de68d9b173ee657115dd0e584c2365b7954253a5
Author:     Thomas Gleixner <[EMAIL PROTECTED]>
AuthorDate: Fri Oct 12 23:04:06 2007 +0200
Committer:  Thomas Gleixner <[EMAIL PROTECTED]>
CommitDate: Fri Oct 12 23:04:06 2007 +0200

    clockevents: fix periodic broadcast for oneshot devices
    The next_event member of the clock event device is used to keep track
    of the next periodic event. For one shot only devices it is wrong to
    clear the variable, as the next event will be based on it.
    Pointed out by Ralf Baechle
    Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
    Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
    Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
 kernel/time/tick-broadcast.c |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

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 git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to