From: Arjan van de Ven Date: Tue, 18 Nov 2008 14:56:51 +0000 (-0800) Subject: suspend: use WARN not WARN_ON to print the message X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=a6a0c4ca7edb378a8a7332501f097089cb1051c4;p=GitHub%2FLineageOS%2Fandroid_kernel_samsung_universal7580.git 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 Signed-off-by: Linus Torvalds --- diff --git a/kernel/power/main.c b/kernel/power/main.c index 19122cf6d82..b8f7ce9473e 100644 --- a/kernel/power/main.c +++ b/kernel/power/main.c @@ -174,7 +174,7 @@ static void suspend_test_finish(const char *label) * has some performance issues. The stack dump of a WARN_ON * is more likely to get the right attention than a printk... */ - WARN_ON(msec > (TEST_SUSPEND_SECONDS * 1000)); + WARN(msec > (TEST_SUSPEND_SECONDS * 1000), "Component: %s\n", label); } #else