commit | 18ed61da985c57eea3fe8038b13fa2837c9b3c3f | [log] [tgz] |
---|---|---|
author | Thomas Gleixner <tglx@linutronix.de> | Fri Nov 27 15:24:44 2009 +0100 |
committer | Thomas Gleixner <tglx@linutronix.de> | Fri Nov 27 20:37:41 2009 +0100 |
tree | 76f4088ded6203e981438b53b04317f73f27a82b | |
parent | c8bc6f3c806f1fcbfdbf0b1ff6c52dba59192d3b [diff] |
x86: hpet: Make WARN_ON understandable Andrew complained rightly that the WARN_ON in hpet_next_event() is confusing and the code comment not really helpful. Change it to WARN_ONCE and print the reason in clear text. Change the comment to explain what kind of hardware wreckage we deal with. Pointed-out-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Venki Pallipadi <venkatesh.pallipadi@intel.com>