<snip> > > > Those patches weren't applied to linux-omap yet, so this change should > > > be melded into the patch that introduced it. It's better to resend that > > > patch then to create a messed up bisect line. > > > > > > -- > > > balbi > > > > Of course they were merged. I saw this warning when I compiled linux-omap, > > when sending in that pin-muxing patch. > > You're right, at first look I thought this was for omap_hdq.c :-p > > Anyways, this patch should go also to Wim. Please send a copy of this > patch to him so he can apply to his tree as well, btw, here's > his mail: > > Wim Van Sebroeck <wim@xxxxxxxxx> > Done. I'm guessing I don't need to CC linux-omap on that. Let me know if I should have. I've sent it to Wim, with a CC to you (Felipe). - Anand -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
