From: Stephen Warren <swarren@wwwdotorg.org>
To: Martin Sperl <kernel@martin.sperl.org>
Cc: Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
broonie <broonie@kernel.org>,
lee@kernel.org, linux-spi@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: randconfig build error with next-20150413, in drivers/spi/spi-bcm2835.c
Date: Mon, 13 Apr 2015 11:06:25 -0600 [thread overview]
Message-ID: <552BF791.1040309@wwwdotorg.org> (raw)
In-Reply-To: <CA+r1ZhhhTu+X6bCeparH-BO=+Gs_BA4aPPF7A=E15x2QWUpYUA@mail.gmail.com>
On 04/13/2015 10:52 AM, Jim Davis wrote:
> Building with the attached random configuration file,
>
> drivers/spi/spi-bcm2835.c: In function 'chip_match_name':
> drivers/spi/spi-bcm2835.c:356:21: error: dereferencing pointer to
> incomplete type
> return !strcmp(chip->label, data);
> ^
> drivers/spi/spi-bcm2835.c: In function 'bcm2835_spi_setup':
> drivers/spi/spi-bcm2835.c:382:2: error: implicit declaration of
> function 'gpiochip_find' [-Werror=implicit-function-declaration]
> chip = gpiochip_find("pinctrl-bcm2835", chip_match_name);
> ^
> drivers/spi/spi-bcm2835.c:382:7: warning: assignment makes pointer
> from integer without a cast
> chip = gpiochip_find("pinctrl-bcm2835", chip_match_name);
> ^
> drivers/spi/spi-bcm2835.c:387:21: error: dereferencing pointer to
> incomplete type
> spi->cs_gpio = chip->base + 8 - spi->chip_select;
> ^
> drivers/spi/spi-bcm2835.c: In function 'chip_match_name':
> drivers/spi/spi-bcm2835.c:357:1: warning: control reaches end of
> non-void function [-Wreturn-type]
> }
> ^
Martin,
I think you need to update spi-bcm2835's Kconfig to add a dependency on
GPIO.
prev parent reply other threads:[~2015-04-13 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 16:52 randconfig build error with next-20150413, in drivers/spi/spi-bcm2835.c Jim Davis
2015-04-13 16:52 ` Jim Davis
2015-04-13 17:06 ` Stephen Warren [this message]
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=552BF791.1040309@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@kernel.org \
--cc=jim.epost@gmail.com \
--cc=kernel@martin.sperl.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--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 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.