| commit | 61c22c34c6f80a8e89cff5ff717627c54cc14fd4 | |
| author | Thomas Gleixner <tglx@linutronix.de> | |
| Tue, 9 Sep 2008 19:38:57 +0000 (9 21:38 +0200) | ||
| committer | Thomas Gleixner <tglx@linutronix.de> | |
| Tue, 9 Sep 2008 20:20:01 +0000 (9 22:20 +0200) | ||
| tree | 33349263152d3ed4fd7d65e4c3d60340e6676b5c | treesnapshot (tar.gz zip) |
| parent | 82a28c794f27aac17d7a3ebd7f14d731a11a5532 | commitdiff |
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>
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>
| kernel/time/tick-oneshot.c | diffblobblamehistory |