On Fri, Sep 14, 2012 at 12:20 PM, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > Given the tested-by's that are rolling in, I will assume that people > are hitting this problem in 3.5 and perhaps earlier kernels, so I > scheduled the fix for 3.6, with a -stable backport. Yes, I just checked an Overo setup here that is running 3.2 and it has the same issue. So your plan for 3.6 and -stable is a good one. Steve -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
