On Mon, Feb 11, 2013 at 10:21 PM, Rob Herring <robherring2@xxxxxxxxx> wrote: > On 02/11/2013 04:18 PM, Grant Likely wrote: >> On Mon, Feb 11, 2013 at 7:54 PM, Rob Herring <robherring2@xxxxxxxxx> wrote: >>> I found the problem. of_get_next_available_child -> >>> of_device_is_available -> of_get_property -> of_get_property. An >>> unlocked version of of_device_is_available is needed here. >> >> Oops, I had testbooted on a single core machine which would mask the >> issue. I've crafted a fix and am posting it for review before I apply >> it. >> > > I'm in the process of applying Stephen's fix. I didn't actually see Stephen's fix until just now, after I had already written, posted and pushed out basically the same thing. :-) g. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
