On Thu, Apr 21, 2011 at 04:29:15AM +0100, Ben Hutchings wrote: > > We got a few new quirks added for AMD hardware platforms that fix > > problems. > > Maybe, but I still haven't seen anyone explain what those problems are!
I'll let the AMD people answer this. > > It took 3 patches to get there, yes, but now, as time goes > > on, adding new ones is even easier as the .32 code matches the .39 code > > in this area due to these patches being added. > > > > Now if you find problems in these, great, let me know and I will work to > > resolve them. > > > > As for regressions, what are you referring to? > > These are the regressions I'm aware of in the last few updates: > > 2.6.32.36: 'x86: Cleanup highmap after brk is concluded' broke > hibernation on x86-64 and some x86-32 machines (reverted in .37) > 2.6.32.36: 'signal: Prevent rt_sigqueueinfo and rt_tgsigqueueinfo from > spoofing the signal code' broke glibc aio (fixed in .37) > 2.6.32.34: powerpc kdump/kexec changes didn't compile on UP or 32-bit > (fixed in .37) > 2.6.32.30: 'x86 quirk: Fix polarity for IRQ0 pin2 override on SB800 > systems' broke the revision check for other quirks (fixed in .34) Bugs are always a part of life, the fact that we fix them is what is important. > 2.6.32.29: 'USB: Prevent buggy hubs from crashing the USB stack' broke > MUSB on BeagleBoards (still unfixed?) This woried me, as I don't recall anyone notifying me of it. Then I saw your revert, and I noticed that all you really need to resolve this is commit id ec95d35a6bd0047f05fe8a21e6c52f8bb418da55 to be added to the tree. I'll go queue that one up for the next .32-stable tree. So all should be resolved now, right? thanks, greg k-h _______________________________________________ stable mailing list [email protected] http://linux.kernel.org/mailman/listinfo/stable
