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

    udldrmfb: udl_get_edid: drop unneeded i--

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:
     udldrmfb-udl_get_edid-drop-unneeded-i.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 <[email protected]> know about it.


>From 7b4cf994e4c6ba48872bb25253cc393b7fb74c82 Mon Sep 17 00:00:00 2001
From: Hans de Goede <[email protected]>
Date: Fri, 11 Jan 2013 12:08:58 +0100
Subject: udldrmfb: udl_get_edid: drop unneeded i--

From: Hans de Goede <[email protected]>

commit 7b4cf994e4c6ba48872bb25253cc393b7fb74c82 upstream.

This is a left-over from when udl_get_edid returned the amount of bytes
successfully read, which it no longer does.

Signed-off-by: Hans de Goede <[email protected]>
Signed-off-by: Dave Airlie <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/gpu/drm/udl/udl_connector.c |    1 -
 1 file changed, 1 deletion(-)

--- a/drivers/gpu/drm/udl/udl_connector.c
+++ b/drivers/gpu/drm/udl/udl_connector.c
@@ -40,7 +40,6 @@ static u8 *udl_get_edid(struct udl_devic
                                      HZ);
                if (ret < 1) {
                        DRM_ERROR("Read EDID byte %d failed err %x\n", i, ret);
-                       i--;
                        goto error;
                }
                block[i] = rbuf[1];


Patches currently in stable-queue which might be from [email protected] are

queue-3.4/udldrmfb-udl_get_edid-usb_control_msg-buffer-must-not-be-on-the-stack.patch
queue-3.4/epoll-prevent-missed-events-on-epoll_ctl_mod.patch
queue-3.4/udldrmfb-udl_get_edid-drop-unneeded-i.patch
queue-3.4/udldrmfb-fix-edid-not-working-with-monitors-with-edid.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to