From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Fabian Vogt <fabian@ritter-vogt.de>
Subject: linux-next: build failure after merge of the final tree (gpio tree related)
Date: Wed, 5 Mar 2014 17:35:59 +1100 [thread overview]
Message-ID: <20140305173559.0b50971a1ab88a16bee8819c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpio/gpio-zevio.c: In function 'zevio_gpio_port_get':
drivers/gpio/gpio-zevio.c:70:2: error: implicit declaration of function 'IOMEM' [-Werror=implicit-function-declaration]
return readl(IOMEM(c->chip.regs + section_offset + port_offset));
^
drivers/gpio/gpio-zevio.c:70:2: warning: passing argument 1 of 'readl' makes pointer from integer without a cast [enabled by default]
In file included from include/linux/io.h:22:0,
from drivers/gpio/gpio-zevio.c:15:
arch/powerpc/include/asm/io-defs.h:6:16: note: expected 'const volatile void *' but argument is of type 'int'
DEF_PCI_AC_RET(readl, u32, (const PCI_IO_ADDR addr), (addr), mem, addr)
^
arch/powerpc/include/asm/io.h:577:19: note: in definition of macro 'DEF_PCI_AC_RET'
static inline ret name at \
^
drivers/gpio/gpio-zevio.c: In function 'zevio_gpio_port_set':
drivers/gpio/gpio-zevio.c:77:2: warning: passing argument 2 of 'writel' makes pointer from integer without a cast [enabled by default]
writel(val, IOMEM(c->chip.regs + section_offset + port_offset));
^
In file included from include/linux/io.h:22:0,
from drivers/gpio/gpio-zevio.c:15:
arch/powerpc/include/asm/io-defs.h:11:18: note: expected 'volatile void *' but argument is of type 'int'
DEF_PCI_AC_NORET(writel, (u32 val, PCI_IO_ADDR addr), (val, addr), mem, addr)
^
arch/powerpc/include/asm/io.h:585:20: note: in definition of macro 'DEF_PCI_AC_NORET'
static inline void name at \
^
Caused by commit 9af4d80ba566 ("gpio: New driver for LSI ZEVIO SoCs").
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-03-05 6:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 6:35 Stephen Rothwell [this message]
2014-03-05 7:16 ` linux-next: build failure after merge of the final tree (gpio tree related) Linus Walleij
2014-03-05 16:42 ` Fabian Vogt
-- strict thread matches above, loose matches on Subject: below --
2013-12-23 4:54 Stephen Rothwell
2013-10-29 9:10 Stephen Rothwell
2013-10-29 13:25 ` Linus Walleij
2013-10-30 0:56 ` Alex Courbot
2013-10-28 14:12 Stephen Rothwell
2013-10-29 13:28 ` Linus Walleij
2012-02-06 4:23 Stephen Rothwell
2012-02-06 6:07 ` Grant Likely
2012-02-06 14:02 ` Mark Brown
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=20140305173559.0b50971a1ab88a16bee8819c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=fabian@ritter-vogt.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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).