Return-path: Received: from smtp.nokia.com ([192.100.105.134]:36768 "EHLO mgw-mx09.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756602Ab0JFP2p (ORCPT ); Wed, 6 Oct 2010 11:28:45 -0400 Subject: Re: [PATCH] omap: zoom2/3: fix build caused by wl1271 support From: Luciano Coelho To: "ext Gadiyar, Anand" Cc: "John W. Linville" , ext Tony Lindgren , "linux-omap@vger.kernel.org" , "linux-wireless@vger.kernel.org" , Ohad Ben-Cohen In-Reply-To: References: <1285965206-17777-1-git-send-email-gadiyar@ti.com> <20101001231026.GH3117@atomide.com> <1286279588.15401.28.camel@chilepepper> <1286280426.15401.29.camel@chilepepper> <1286284790.15401.53.camel@chilepepper> <1286311187.2793.7.camel@powerslave> <20101006135221.GE2472@tuxdriver.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 06 Oct 2010 18:27:49 +0300 Message-ID: <1286378869.6731.7.camel@powerslave> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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.