* Grazvydas Ignotas <notasas@xxxxxxxxx> [100705 14:43]: > On Mon, Jul 5, 2010 at 10:36 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > We should just print a warning and return an error. Then we should > > also start checking the return values for omap_mux_init_gpio > > now that the code is converted over to use the new mux code. > > Hm, not sure about return checking, what omap2_mmc_mux() can do when > it sees omap_mux_init_gpio failing because of that inevitable gpio126 > multipath error? Heh, right :) I guess in that case omap2_mmc_mux should not do anything and assume the board-*.c file has set up the muxing. Regards, Tony -- 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
