ia64/linux-2.6.18-xen.hg

changeset 789:25cc543a02e8

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>
author Keir Fraser <keir.fraser@citrix.com>
date Tue Feb 03 13:59:17 2009 +0000 (2009-02-03)
parents 26ddc59c674d
children 77e3b255381e
files drivers/xen/fbfront/xenfb.c
line diff
     1.1 --- a/drivers/xen/fbfront/xenfb.c	Fri Jan 30 10:54:10 2009 +0000
     1.2 +++ b/drivers/xen/fbfront/xenfb.c	Tue Feb 03 13:59:17 2009 +0000
     1.3 @@ -211,7 +211,7 @@ static void xenfb_update_screen(struct x
     1.4  		return;
     1.5  
     1.6  	mutex_lock(&info->mm_lock);
     1.7 -	
     1.8 +
     1.9  	spin_lock_irqsave(&info->dirty_lock, flags);
    1.10  	if (info->dirty){
    1.11  		info->dirty = 0;
    1.12 @@ -837,7 +837,7 @@ static void xenfb_backend_changed(struct
    1.13  			if (IS_ERR(info->kthread)) {
    1.14  				info->kthread = NULL;
    1.15  				xenbus_dev_fatal(dev, PTR_ERR(info->kthread),
    1.16 -						"register_framebuffer");
    1.17 +						"xenfb_thread");
    1.18  			}
    1.19  		}
    1.20  		break;