On Mon, Dec 08, 2014 at 07:54:08AM -0600, Nishanth Menon wrote: > On 12/08/2014 06:22 AM, Russell King - ARM Linux wrote: > > On Mon, Dec 08, 2014 at 08:54:18PM +0900, Tomasz Figa wrote: > >> 2014-12-06 1:23 GMT+09:00 Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>: > >>> Given where we are in the cycle (-final likely this weekend) the only > >>> thing we can do right now is to drop the patch set; exynos (and mvebu) > >>> will have to wait another cycle until this patch set (hopefully in a > >>> revised form) can be merged. > >> > >> Or a fix could be queued on top of this. Since (I believe) this series > >> has been queued for 3.19, we have 6 or 7 RC releases ahead, which > >> could be used for the purpose of fixing things (as they are supposed > >> to?). > > > > They were merged on 27th November, so they would've been in linux-next > > from about last Monday. Nishanth reported a failure on Friday, the > > For what ever it is worth, the l2c changes actually appeared on > Thursday CST (next-20141204). Found the regression against > next-20141203 tag and it took me a day to track it down (after looking > at a few other regressions as well).. I wonder if that's because I didn't push my tree out until Tuesday-ish. It takes around 48 hours between when I push stuff out to it appearing in linux-next, which is not particularly desirable, but unavoidable due to timezone differences. I did decide that I wouldn't push it out the same day I merged it because I wanted it to run through my build/boot system, which it did successfully, but then my OMAP4 build doesn't have CPU idle enabled (and as you've identified, when CPU idle is disabled, it works.) The problem there is that if I decide not to push some merged changes out, it takes several days before I get around to touching the kernel tree again. Hence why it took from Thursday until Tuesday for it to eventually get pushed out. -- FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up according to speedtest.net. -- 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
