From: Luciano Coelho <luciano.coelho@nokia.com>
To: "ext Gadiyar, Anand" <gadiyar@ti.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
ext Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Ohad Ben-Cohen <ohad@wizery.com>
Subject: Re: [PATCH] omap: zoom2/3: fix build caused by wl1271 support
Date: Wed, 06 Oct 2010 18:27:49 +0300 [thread overview]
Message-ID: <1286378869.6731.7.camel@powerslave> (raw)
In-Reply-To: <AANLkTinHA+JS1MObanawFF8ktW6OEMGr7CnJhakUetPz@mail.gmail.com>
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.
next prev parent reply other threads:[~2010-10-06 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 20:33 [PATCH] omap: zoom2/3: fix build caused by wl1271 support Anand Gadiyar
2010-10-01 23:10 ` Tony Lindgren
2010-10-05 11:53 ` Luciano Coelho
2010-10-05 12:07 ` Luciano Coelho
2010-10-05 13:19 ` Luciano Coelho
2010-10-05 20:39 ` Luciano Coelho
2010-10-06 13:52 ` John W. Linville
2010-10-06 14:01 ` Gadiyar, Anand
2010-10-06 15:27 ` Luciano Coelho [this message]
2010-10-06 15:30 ` John W. Linville
2010-10-06 15:55 ` Luciano Coelho
2010-10-06 19:34 ` Luciano Coelho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1286378869.6731.7.camel@powerslave \
--to=luciano.coelho@nokia.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ohad@wizery.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).