drm/vmwgfx: Fix an fb unlocking bug

A regression introduced when the master ttm lock was split into two.

Reported-and-tested-by: Brian Paul <brianp@vmware.com>
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>

diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_fb.c b/drivers/gpu/drm/vmwgfx/vmwgfx_fb.c
index 0a474f391fad0157d8a51e5aa2e50d6c4aec69ec..e2d40ebd545583af20c816e88dc4cd47ef306f3d 100644 (file)
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_fb.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_fb.c
@@ -402,12 +402,12 @@ static int vmw_fb_create_bo(struct vmw_private *vmw_priv,
 
        *out = vmw_bo;
 
-       ttm_write_unlock(&vmw_priv->fbdev_master.lock);
+       ttm_write_unlock(&vmw_priv->reservation_sem);
 
        return 0;
 
 err_unlock:
-       ttm_write_unlock(&vmw_priv->fbdev_master.lock);
+       ttm_write_unlock(&vmw_priv->reservation_sem);
        return ret;
 }