Thomas Gleixner 61c22c34c6 clockevents: remove WARN_ON which was used to gather information ... The issue of the endless reprogramming loop due to a too small min_delta_ns was fixed with the previous updates of the clock events code, but we had no information about the spread of this problem. I added a WARN_ON to get automated information via kerneloops.org and to get some direct reports, which allowed me to analyse the affected machines. The WARN_ON has served its purpose and would be annoying for a release kernel. Remove it and just keep the information about the increase of the min_delta_ns value. Signed-off-by: Thomas Gleixner <tglx@linutronix.de>		2008-09-09 22:20:01 +02:00
..
Kconfig	…
Makefile	…
clockevents.c	clockevents: prevent clockevent event_handler ending up handler_noop	2008-09-05 11:11:51 +02:00
clocksource.c	…
jiffies.c	…
ntp.c	ntp: fix calculation of the next jiffie to trigger RTC sync	2008-09-06 15:31:48 +02:00
tick-broadcast.c	clockevents: broadcast fixup possible waiters	2008-09-06 07:21:17 +02:00
tick-common.c	clockevents: prevent clockevent event_handler ending up handler_noop	2008-09-05 11:11:51 +02:00
tick-internal.h	clockevents: prevent endless loop lockup	2008-09-05 11:11:53 +02:00
tick-oneshot.c	clockevents: remove WARN_ON which was used to gather information	2008-09-09 22:20:01 +02:00
tick-sched.c	sched_clock: fix NOHZ interaction	2008-09-05 18:14:08 +02:00
timekeeping.c	…
timer_list.c	…
timer_stats.c	…