On 07/02/2012 12:12 AM, John Stultz wrote: > On 07/01/2012 11:29 AM, John Stultz wrote: >> TODOs: >> * Chase down the futex/hrtimer interaction to see if this could >> be triggered in any other way. >> * Get Tglx's input/ack >> * Generate a backport for pre-v3.4 kernels > So while still waiting for feedback on the clock_was_set() change, I went > ahead > and generated backports for most of the stable kernels on kernel.org. >
I've tested on a well-known enterprise distro ;), as well as it's more public variant with the latest top-of-tree kernel + this second patchset across a fairly wide selection of systems [AMD and Intel, large and small] and don't see any issues. (I haven't taken tglx's comments into account yet though ... this is just an indication that the direction of the patch seems correct) P. -- 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
