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

    atl1c: duplicate atl1c_get_tpd

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

The filename of the patch is:
     atl1c-duplicate-atl1c_get_tpd.patch
and it can be found in the queue-2.6.32 subdirectory.

If you, or anyone else, feels it should not be added to the 2.6.32 longterm 
tree,
please let <[email protected]> know about it.


>From 678b77e265f6d66f1e68f3d095841c44ba5ab112 Mon Sep 17 00:00:00 2001
From: Jie Yang <[email protected]>
Date: Tue, 27 Oct 2009 22:31:19 -0700
Subject: atl1c: duplicate atl1c_get_tpd

From: Jie Yang <[email protected]>

commit 678b77e265f6d66f1e68f3d095841c44ba5ab112 upstream.

remove duplicate atl1c_get_tpd, it may cause hardware to send wrong packets.

Signed-off-by: Jie Yang <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Cc: Willy Tarreau <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/net/atl1c/atl1c_main.c |    2 --
 1 file changed, 2 deletions(-)

--- a/drivers/net/atl1c/atl1c_main.c
+++ b/drivers/net/atl1c/atl1c_main.c
@@ -1976,8 +1976,6 @@ static void atl1c_tx_map(struct atl1c_ad
                else {
                        use_tpd = atl1c_get_tpd(adapter, type);
                        memcpy(use_tpd, tpd, sizeof(struct atl1c_tpd_desc));
-                       use_tpd = atl1c_get_tpd(adapter, type);
-                       memcpy(use_tpd, tpd, sizeof(struct atl1c_tpd_desc));
                }
                buffer_info = atl1c_get_tx_buffer(adapter, use_tpd);
                buffer_info->length = buf_len - mapped_len;


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

/home/gregkh/linux/longterm/longterm-queue-2.6.32/queue-2.6.32/atl1c-duplicate-atl1c_get_tpd.patch

_______________________________________________
stable mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/stable

Reply via email to