On Sun, Jan 20, 2013 at 1:24 PM, Tetsuo Handa
<[email protected]> wrote:
> While (1) was fixed by now, I can't bisect (2) since (1) is preventing (2)
> from
> printing messages.
I usually bisect like this:
1. Get hold of the patch fixing the boot regression:
git format-patch
f5565295892eb93c3191aa241405fe8b685542d6^..f5565295892eb93c3191aa241405fe8b685542d6
2. At each iterative step using git bisect:
patch -p1 < 0001-ARM-7610-1-versatile-bump-IRQ-numbers.patch
3. Boot/trial-and-horror
4. git reset --hard HEAD
To nullify the effects of the patch.
5. git bisect [good|bad]
6. Iterate from (2) until you find the bug.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
