> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Reizer, Eyal > Sent: Sunday, February 20, 2011 4:20 PM > To: tony@xxxxxxxxxxx > Cc: linux-omap@xxxxxxxxxxxxxxx > Subject: Re: Re: Ping-> Subject: [PATCH] omap: omap3evm: add support for > the WL12xx WLAN module to the omap3evm > > On Thu, 2011-02-17 at 14:20 -0800, Tony Lindgren wrote: > > * Reizer, Eyal <eyalr@xxxxxx> [110215 07:11]: > > > Dear Tony, > > > > > > I did not receive any comments to the patch I have send in the > following link: > > > > > > http://marc.info/?l=linux-omap&m=129612179900695&w=2 > > > > > > Are there any issues with excepting this patch? > > > > Pushing to devel-board branch for the upcoming merge window. > > Can you please check it's working? I had to merge some other > > evm board changes manually.. > > > > Tony > > Dear Tony, > > As you requested, I have tested the devel-board branch this morning and > found one merge issue. > I see that there are now two mux arrays, one for omap35x and one for > omap36x. > You have merged the muxes changes to the omap35x_board_mux[] array, but > have missed the other structure called omap36x_board_mux[]. > The same change should be merged there as well. > The result is that it would work OK on an evm with an omap35x SOM but > not on aboard with an omap37x SOM. > Please find below a fix for that. > Eyal, I am assuming that you will be sending an updated version of the patch fixing some of the issues pointed in this response: http://marc.info/?l=linux-omap&m=129820402332111&w=2 You can add the patch below to updated submission. ~sanjeev > Best Regards, > Eyal Reizer > [snip]...[snip] -- 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
