On Mon, Apr 29, 2013 at 9:48 PM, James Hogan <james.hogan@xxxxxxxxxx> wrote: > On 29/04/13 19:15, Bryan Wu wrote: >> Hi Patrice and Linus, >> >> I'm running linux-next on my Tegra 30 system everyday. But since >> next-20130426 release, the linux-next kernel will hang on my Tegra 30 >> boards like Cardhu and Beaver. >> >> After some bisect and comparing to next-20130424, I found the commit >> "pinctrl: move subsystem mutex to pinctrl_dev struct" introduced this >> issue. If I simply revert this patch in next-20130429, system boots up >> as before. >> >> Could you please help to check this? > > I spent a while tracking this one down today too, then found it was > already fixed. See the patch "[PATCH, for-next] pinctrl: fix mutex > deadlock in get_pinctrl_dev_from_of_node()" from Daniel Mack. This one is now in Torvald's tree. Thanks, Linus Walleij -- 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
