On Thu, Feb 28, 2013 at 02:20:40AM +0100, Thomas Bork wrote:
> Hi @all,
>
> after a bug report of a user of 2.6.32.60 I searched the changes for
> r8169 in newer kernel trees.
> The user had a RTL8102E, which is not correctly working with the vanilla
> r8169.c.
>
> There is a change for correctly driving rtl8102:
>
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=d24e9aafe5d5dfdf6d114b29e67f8afd5fae5ef0
>
>
> This change was not backported to 2.6.3x.y. Can you tell me the reason why?
Very likely because nobody submitted it to stable@ so it was not considered
for backporting. And the commit message is unclear about the fact that it
had to be backported too :
r8169: correct settings of rtl8102e.
Adjust and remove certain settings of RTL8102E which are for previous chips.
Signed-off-by: Hayes Wang <[email protected]>
Acked-off-by: Francois Romieu <[email protected]>
(...)
> While at it, I backported
>
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=3a42cce923b0242d0293cae0a162601afa89d552
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=7106159f8bd33bd5e5b0ea2c87e499117fc22c69
>
> also.
OK, I can queue these 3 patches for the next 2.6.32.
Thanks Thomas,
Willy
--
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
