| commit | bc3ac469af00b0e5b7799c127d00b6650fab5587 | |
| author | Thomas Gleixner <tglx@linutronix.de> | |
| Tue, 9 Sep 2008 19:38:57 +0000 (9 21:38 +0200) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Thu, 9 Oct 2008 03:23:05 +0000 (8 20:23 -0700) | ||
| tree | ee387ef074a6f180e030fb9b83932c62573a1846 | treesnapshot (tar.gz zip) |
| parent | e0d725a2b5770e9631b893c0ee37396569767de5 | commitdiff |
clockevents: remove WARN_ON which was used to gather information
commit 61c22c34c6f80a8e89cff5ff717627c54cc14fd4 upstream
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 61c22c34c6f80a8e89cff5ff717627c54cc14fd4 upstream
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| kernel/time/tick-oneshot.c | diffblobblamehistory |