All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Luciano Coelho <luciano.coelho-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
Cc: "ext Gadiyar, Anand" <gadiyar-l0cyMroinI0@public.gmane.org>,
	ext Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Ohad Ben-Cohen <ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] omap: zoom2/3: fix build caused by wl1271 support
Date: Wed, 6 Oct 2010 11:30:25 -0400	[thread overview]
Message-ID: <20101006153025.GG2472@tuxdriver.com> (raw)
In-Reply-To: <1286378869.6731.7.camel@powerslave>

On Wed, Oct 06, 2010 at 06:27:49PM +0300, Luciano Coelho wrote:
> 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.

OK, that's fine -- do you have the commit ID and the tree that has it?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: Luciano Coelho <luciano.coelho@nokia.com>
Cc: "ext Gadiyar, Anand" <gadiyar@ti.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, 6 Oct 2010 11:30:25 -0400	[thread overview]
Message-ID: <20101006153025.GG2472@tuxdriver.com> (raw)
In-Reply-To: <1286378869.6731.7.camel@powerslave>

On Wed, Oct 06, 2010 at 06:27:49PM +0300, Luciano Coelho wrote:
> 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.

OK, that's fine -- do you have the commit ID and the tree that has it?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2010-10-06 15:30 UTC|newest]

Thread overview: 16+ 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 14:01               ` Gadiyar, Anand
     [not found]               ` <AANLkTinHA+JS1MObanawFF8ktW6OEMGr7CnJhakUetPz-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-06 15:27                 ` Luciano Coelho
2010-10-06 15:27                   ` Luciano Coelho
2010-10-06 15:30                   ` John W. Linville [this message]
2010-10-06 15:30                     ` John W. Linville
2010-10-06 15:55                     ` Luciano Coelho
2010-10-06 19:34                       ` 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=20101006153025.GG2472@tuxdriver.com \
    --to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
    --cc=gadiyar-l0cyMroinI0@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=luciano.coelho-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
    --cc=ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.