| commit | c8a1d398de70a7774359b4720c392891cdd485f9 | |
| author | Thomas Gleixner <tglx@linutronix.de> | |
| Fri, 12 Oct 2007 21:04:06 +0000 (12 23:04 +0200) | ||
| committer | Thomas Gleixner <tglx@inhelltoy.tec.linutronix.de> | |
| Fri, 12 Oct 2007 21:04:06 +0000 (12 23:04 +0200) | ||
| tree | d49de224f33705dd9549d338605578a84dbddf04 | treesnapshot (tar.gz zip) |
| parent | de68d9b173ee657115dd0e584c2365b7954253a5 | commitdiff |
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 <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
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 <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
| kernel/time/tick-broadcast.c | diffblobblamehistory |