Skip to contentSkip to conversation

Missed Cc for stable

DISCUSSION Larry Finger 2 participants 2 messages Apr 21, 2012 – Apr 23, 2012

lore
Share & tools
lore

Larry Finger

author Tested-by Alberto Lago Ballesteros Tested-by Adrian
#0 lore raw

Greg,

I missed a Cc for stable in this patch:

================================================
commit 2080913e017ab9f88379d93fd09546ad95faf87b

Author: Larry Finger <[email protected]>
Date:   Sat Feb 25 18:10:21 2012 -0600

staging: r8712u: Fix regression caused by commit 8c213fa

In commit 8c213fa "staging: r8712u: Use asynchronous firmware loading", the command to release the firmware was placed in the wrong routine.

In combination with the bug introduced in commit a5ee652 "staging: r8712u:
Interface-state not fully tracked", the driver attempts to upload firmware that had already been released. This bug is the source of one of the problems in https://bugs.archlinux.org/task/27996#comment89833.

==============================================

Thanks,

Larry

#1 lore raw
Quoted 19 lines · Larry Finger

Greg,

I missed a Cc for stable in this patch:

================================================
commit 2080913e017ab9f88379d93fd09546ad95faf87b

Author: Larry Finger <[email protected]>
Date:   Sat Feb 25 18:10:21 2012 -0600

staging: r8712u: Fix regression caused by commit 8c213fa

In commit 8c213fa "staging: r8712u: Use asynchronous firmware loading", the command to release the firmware was placed in the wrong routine.

In combination with the bug introduced in commit a5ee652 "staging: r8712u:
Interface-state not fully tracked", the driver attempts to upload firmware that had already been released. This bug is the source of one of the problems in https://bugs.archlinux.org/task/27996#comment89833.

Quoted 5 lines

==============================================

Now applied to the 3.3-stable tree.

thanks,

greg k-h