On Wed, Jul 30, 2014 at 04:15:21AM -0700, Christoph Hellwig wrote: > On Wed, Jul 30, 2014 at 11:55:41AM +0800, Fengguang Wu wrote: > > Greetings, > > > > 0day kernel testing robot got the below dmesg and the first bad commit is > > How does this manage to trip over a 2 year old commit now? The bug is first discovered in linux-next, then the older kernel releases (v3.15, v3.14, ...) are tested step by step, until it's found to be introduced between v3.5 and v3.6. Then bisect can be started: git bisect start v3.6 v3.5 -- Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
