fbfront: Improve diagnostics when kthread_run() fails

Failure is reported with xenbus_dev_fatal(..."register_framebuffer"),
which was already suboptimal before it got moved away from
register_framebuffer(), and is outright misleading now.

Signed-off-by: Markus Armbruster <armbru@redhat.com>

diff --git a/drivers/xen/fbfront/xenfb.c b/drivers/xen/fbfront/xenfb.c
index a98712768dfdacfac30510dc338e76b330ef028c..d6155a45bb3163110b11e01b7a43bb8082d3c5f4 100644 (file)
--- a/drivers/xen/fbfront/xenfb.c
+++ b/drivers/xen/fbfront/xenfb.c
@@ -211,7 +211,7 @@ static void xenfb_update_screen(struct xenfb_info *info)
                return;
 
        mutex_lock(&info->mm_lock);
-       
+
        spin_lock_irqsave(&info->dirty_lock, flags);
        if (info->dirty){
                info->dirty = 0;
@@ -837,7 +837,7 @@ static void xenfb_backend_changed(struct xenbus_device *dev,
                        if (IS_ERR(info->kthread)) {
                                info->kthread = NULL;
                                xenbus_dev_fatal(dev, PTR_ERR(info->kthread),
-                                               "register_framebuffer");
+                                               "xenfb_thread");
                        }
                }
                break;