On Tue, Jun 14, 2016 at 06:30:56PM -0700, Greg KH wrote: > As the patch was tagged with 3.10+, I assumed that it was safe to be > merged to those older kernels, otherwise I would never have done so. We > do have ways to mark external things like this for stable patches, it's > a great help when doing backports. I guess only 3.14.72 was affected in the end. 3.18.35 has the fix but my understanding is that after 3.17 it's OK. Apparently it's not yet queued for 3.16. Jiri has queued it for 3.12 but not yet released it. For 3.10 I only pick patches that are already in a 3.14 release so I didn't have the time to backport it to 3.10 yet as the preview started before the release. Overall the regression lived only 8 days in a single branch, I guess it shows that our process works rather well and limits the exposure to regressions. Brad, it would have been nice to report it to the stable team especially since you rely on these kernels for yours as well. Regards, Willy -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html