Skip to contentSkip to conversation

r8169 stable updates

DISCUSSION Tim Gardner 3 participants 3 messages Apr 30, 2010 – May 7, 2010

lore
Share & tools
lore
#0 lore raw

Francois,

If not already proposed, I think these commits are appropriate for stable updates. Do you agree? They apply cleanly to 2.6.32 and will likely fix the symptoms of this bug: http://bugs.launchpad.net/bugs/562742 (still in test).

4c020a961a812ffae9846b917304cea504c3a733 r8169: use correct barrier between cacheable and non-cacheable memory

78f1cd02457252e1ffbc6caa44a17424a45286b8 r8169: fix broken register writes

908ba2bfd22253f26fa910cd855e4ccffb1467d0 r8169: more broken register writes workaround

rtg

Signature · 1 line
Tim Gardner [email protected]
#1 lore raw

Tim Gardner <[email protected]> :
[...]

Quoted 2 lines

If not already proposed, I think these commits are appropriate for stable updates. Do you agree ?

Yes.

I have just sent those for both 2.6.32-stable and 2.6.33-stable.

Signature · 1 line
Ueimor
#2 lore raw
In reply to Tim Gardner
Quoted 7 lines · Tim Gardner

Francois,

If not already proposed, I think these commits are appropriate for stable updates. Do you agree? They apply cleanly to 2.6.32 and will likely fix the symptoms of this bug:
http://bugs.launchpad.net/bugs/562742 (still in test).

Quoted 7 lines

4c020a961a812ffae9846b917304cea504c3a733 r8169: use correct barrier between cacheable and non-cacheable memory

78f1cd02457252e1ffbc6caa44a17424a45286b8 r8169: fix broken register writes

908ba2bfd22253f26fa910cd855e4ccffb1467d0 r8169: more broken register writes workaround

All now queued up.

thanks,

greg k-h