On Wed, 2010-10-06 at 16:01 +0200, ext Gadiyar, Anand wrote: > >> Hmmm... We got a problem here. This patch breaks builds when we *don't* > >> have "omap: mmc extended to pass host capabilities from board file". We > >> don't have that on wireless-next yet, so builds with zoom boards > >> selected are broken. > >> > >> Any ideas on how to solve this dilemma? I guess the proper way to handle > >> this would be to make the changes proposed in this patch when merging > >> instead of having a normal commit for it, wouldn't it? > > > > Just cherry-pick that change into the branch of your tree that I do > > _not_ pull from. I presume that it is already available in linux-next? > > > > Yup - both patches are in linux-next; that's where we noticed the build break. Ok, I hope the patch applies cleanly in our trees. John, don't you want to do the cherry-pick on your wireless-testing then? If you do it, I can "inherit" that, because I pull from it into my "testing" branch (wl12xx/master). At the moment, w-t is broken too. -- Cheers, Luca. -- 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
