Hi Bjorn On Wed, Apr 22, 2015 at 6:47 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > > I'm not really a fan of this. The NULL pointer oops is a very good clue > all by itself, and it doesn't require any extra code here. It is a pointer to 0x30. For some reason my platform can handle a couple of oops, but if I get a fair amount of them in a short period of time, the whole thing crashes and debugging gets complicated. (no access to dmesg or remote debugging). Therefore this particular bug gave me a bad time. Now that we have located the root of the problem and solved the problem from the root, this particular error will never be hit. I just wanted to save somebody else's time with this patch. All that said, if the other patches are applied, my platform works completely fine. So it is completely your call to accept this or not :) I will resend the patchset without this patch Thanks! -- Ricardo Ribalda -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
