Re: Memory probing fails after 2.6.30 (bisected)

[Anders Eriksson]

hancockrwd@xxxxxxxxx said:
> Think you missed posting which was the actual bad commit it reported?

The last one in the list:
8ecee4620e76aae418bfa0e8cc830e92cb559bbb

That's a merge commit. How do i dig futher into that? My git-fu is lacking...

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/