suspend: use WARN not WARN_ON to print the message

By using WARN(), kerneloops.org can collect which component is causing
the delay and make statistics about that. suspend_test_finish() is
currently the number 2 item but unless we can collect who's causing
it we're not going to be able to fix the hot topic ones..

Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

authored by Arjan van de Ven and committed by Linus Torvalds a6a0c4ca 72b51a6b

+1 -1
+1 -1
kernel/power/main.c
··· 174 174 * has some performance issues. The stack dump of a WARN_ON 175 175 * is more likely to get the right attention than a printk... 176 176 */ 177 - WARN_ON(msec > (TEST_SUSPEND_SECONDS * 1000)); 177 + WARN(msec > (TEST_SUSPEND_SECONDS * 1000), "Component: %s\n", label); 178 178 } 179 179 180 180 #else