* Bryan Wu <cooloney@xxxxxxxxx> [131022 10:47]: > On Tue, Oct 22, 2013 at 10:37 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > * Bryan Wu <cooloney@xxxxxxxxx> [131022 10:23]: > >> On Tue, Oct 22, 2013 at 10:06 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > >> > * Sebastian Reichel <sre@xxxxxxxxxx> [131022 06:02]: > >> >> This patch moves the handling of the chip's enable pin from the board > >> >> code into the driver. It also updates all board-code files using the > >> >> driver to incorporate this change. > >> >> > >> >> This is needed for device tree support of the enable pin. > >> > > >> > This seems safe to merge along with the other LED patches, the > >> > changes to arch/arm/mach-omap2 should not conflict with anything. > >> > > >> > So for the arch/arm/mach-omap2 changes: > >> > > >> > Acked-by: Tony Lindgren <tony@xxxxxxxxxxx> > >> > >> I'm OK for LED parts, will this patch go through omap tree? If so, > >> please add my ack. > >> > >> Acked-by: Bryan Wu <cooloney@xxxxxxxxx> > > > > It's probably best that you take it via with the LED patches. > > > > OK, I will do it. what about PATCH 2 of this patch set? Will you take > care of it? Benoit should take that one, otherwise there's a good chance of pointless merge conflicts with the .dts files. 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
