This is a note to let you know that I've just added the patch titled

    drm/usb: bind driver to correct device

to the 3.4-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     drm-usb-bind-driver-to-correct-device.patch
and it can be found in the queue-3.4 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


>From 9f23de52b64f7fb801fd76f3dd8651a0dc89187b Mon Sep 17 00:00:00 2001
From: Dave Airlie <airl...@redhat.com>
Date: Thu, 7 Feb 2013 10:10:04 +1000
Subject: drm/usb: bind driver to correct device

From: Dave Airlie <airl...@redhat.com>

commit 9f23de52b64f7fb801fd76f3dd8651a0dc89187b upstream.

While looking at plymouth on udl I noticed that plymouth was trying
to use its fb plugin not its drm one, it was trying to drmOpen a driver called
usb not udl, noticed that we actually had out driver pointing at the wrong
device.

Signed-off-by: Dave Airlie <airl...@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>

---
 drivers/gpu/drm/drm_usb.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/gpu/drm/drm_usb.c
+++ b/drivers/gpu/drm/drm_usb.c
@@ -18,7 +18,7 @@ int drm_get_usb_dev(struct usb_interface
 
        usbdev = interface_to_usbdev(interface);
        dev->usbdev = usbdev;
-       dev->dev = &usbdev->dev;
+       dev->dev = &interface->dev;
 
        mutex_lock(&drm_global_mutex);
 


Patches currently in stable-queue which might be from airl...@redhat.com are

queue-3.4/vgacon-vt-clear-buffer-attributes-when-we-load-a-512-character-font-v2.patch
queue-3.4/drm-don-t-add-inferred-modes-for-monitors-that-don-t-support-them.patch
queue-3.4/drm-usb-bind-driver-to-correct-device.patch
queue-3.4/drm-udl-make-usage-as-a-console-safer.patch
queue-3.4/drm-udl-disable-fb_defio-by-default.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to