linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@nokia.com>
To: "Oikarinen Juuso (Nokia-D/Tampere)" <juuso.oikarinen@nokia.com>
Cc: ext Stephen Rothwell <sfr@canb.auug.org.au>,
	"John W. Linville" <linville@tuxdriver.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Paasikivi Teemu.3 (EXT-Ixonos/Tampere)"
	<ext-teemu.3.paasikivi@nokia.com>
Subject: Re: linux-next: build failure after merge of the wireless tree
Date: Wed, 10 Mar 2010 13:19:53 +0200	[thread overview]
Message-ID: <1268219993.10194.82.camel@chilepepper> (raw)
In-Reply-To: <1268200397.10120.459.camel@wimaxnb.nmp.nokia.com>

On Wed, 2010-03-10 at 06:53 +0100, Oikarinen Juuso (Nokia-D/Tampere)
wrote:
> Thinking about it, the assumption is correct. The implementation can
> currently work only on ARM, as the wl1271 requires and out-of-band IRQ
> line which is currently implemented with GPIO's.
> 
> -Juuso
> 
> On Wed, 2010-03-10 at 04:36 +0100, ext Stephen Rothwell wrote:
> > Hi John,
> > 
> > After merging the wireless tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/net/wireless/wl12xx/wl1271_sdio.c:31:23: error: plat/gpio.h: No such file or directory
> > drivers/net/wireless/wl12xx/wl1271_sdio.c: In function 'wl1271_sdio_raw_read':
> > drivers/net/wireless/wl12xx/wl1271_sdio.c:121: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
> > drivers/net/wireless/wl12xx/wl1271_sdio.c: In function 'wl1271_sdio_raw_write':
> > drivers/net/wireless/wl12xx/wl1271_sdio.c:144: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
> > drivers/net/wireless/wl12xx/wl1271_sdio.c: In function 'wl1271_probe':
> > drivers/net/wireless/wl12xx/wl1271_sdio.c:198: error: implicit declaration of function 'gpio_to_irq'
> > 
> > Caused by commit 5129dffebd4eab1749e63bb4a1b7abdc92903227 ("wl1271:
> > Initial SDIO implementation").  I assume this is only meant to be built
> > for arm?

I'll send a patch to fix this problem soon.  Sorry for the trouble.

-- 
Cheers,
Luca.

  reply	other threads:[~2010-03-10 11:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  3:36 linux-next: build failure after merge of the wireless tree Stephen Rothwell
2010-03-10  5:53 ` Juuso Oikarinen
2010-03-10 11:19   ` Luciano Coelho [this message]
2010-03-10 11:22     ` [PATCH] wl1271: Changed wl1271_sdio to be selectable only on ARM Luciano Coelho
2010-06-23  2:51 linux-next: build failure after merge of the wireless tree Stephen Rothwell
2010-06-23 14:57 ` John W. Linville
2011-05-16  2:02 Stephen Rothwell
2011-05-16 18:08 ` John W. Linville
2011-06-23  3:03 Stephen Rothwell
2011-06-23  3:46 ` David Miller
2011-06-28 18:11 ` Gustavo F. Padovan
2011-10-12  2:36 Stephen Rothwell

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=1268219993.10194.82.camel@chilepepper \
    --to=luciano.coelho@nokia.com \
    --cc=ext-teemu.3.paasikivi@nokia.com \
    --cc=juuso.oikarinen@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sfr@canb.auug.org.au \
    /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).