[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1403694435-3180-20-git-send-email-jslaby@suse.cz>
Date: Wed, 25 Jun 2014 13:07:14 +0200
From: Jiri Slaby <jslaby@...e.cz>
To: linux-kernel@...r.kernel.org
Cc: tj@...nel.org, rostedt@...dmis.org, mingo@...hat.com,
akpm@...ux-foundation.org, andi@...stfloor.org,
paulmck@...ux.vnet.ibm.com, pavel@....cz, jirislaby@...il.com,
Vojtech Pavlik <vojtech@...e.cz>, Michael Matz <matz@...e.de>,
Jiri Kosina <jkosina@...e.cz>,
Libor Pechacek <lpechacek@...e.cz>, Jiri Slaby <jslaby@...e.cz>
Subject: [PATCH -repost 20/21] kgr: rephrase the "kGraft failed" message
From: Libor Pechacek <lpechacek@...e.cz>
kGraft not succeeding on the first attempt can hardly be called a
failure. kGraft is merely waiting for sleeping processes to wake up
and get out of the way.
Signed-off-by: Libor Pechacek <lpechacek@...e.cz>
Signed-off-by: Jiri Slaby <jslaby@...e.cz>
---
kernel/kgraft.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/kgraft.c b/kernel/kgraft.c
index 1247f1c60b09..90ef7fba6d0a 100644
--- a/kernel/kgraft.c
+++ b/kernel/kgraft.c
@@ -108,7 +108,7 @@ static void kgr_finalize(void)
static void kgr_work_fn(struct work_struct *work)
{
if (kgr_still_patching()) {
- pr_info("kgr failed after timeout (%d), still in degraded mode\n",
+ pr_info("kgr still in progress after timeout (%d)\n",
KGR_TIMEOUT);
/* recheck again later */
queue_delayed_work(kgr_wq, &kgr_work, KGR_TIMEOUT * HZ);
--
2.0.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists