On Mon, Jan 28, 2013 at 8:28 PM, Tejun Heo <tj@xxxxxxxxxx> wrote: > Hello, guys. > > On Sun, Jan 27, 2013 at 02:01:50PM +0100, Sedat Dilek wrote: >> OK, that bisecting ruined a bit my weekend and showed me again you >> cannot really bisect Linux-Next. >> Sometimes, it is better not to trust the tools blindly and do a >> bisect-on-suspicion. >> Anyway... cultprit found... patch found... applied... all GOOD now. >> ( If I had waited for next Monday's next-20130127 I would not have >> seen what caused the trouble. ). > > Yeah, my usual test setup didn't have async tasks w/o domain so I > failed to notice the breakage. Sorry about the trouble guys and lots > of thanks to Sedat for the firefighting over the weekend. :) > [ CC James ] Hi Tejun, I don't see that git-bisect session as a time of waste, but two hints: 1. People should sent their patches concerning especially Linux-Next fixes not only to LKML but also to <linux-next@xxxxxxxxxxxxxxx> (if this is not known, pointing to James). 2. These patches for Linux-Next should contain a "-next" in their subject-line (use 'git format-patch --subject-prefix="PATCH -next" ...'). Of course, I should have checked the MLs... but for me it was not clear what was the root cause (which subsystem to blame)... I had only some suspicions. Anyway, noone gave me any pointer on how to log bastard logs before my system got frozen (2nd machine not available). I know that is tricky! For a better world... Regards, - Sedat - > -- > tejun -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
