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,
Bruno Randolf <br1@einfach.org>
Subject: linux-next: build failure after merge of the final tree (gpio tree related)
Date: Mon, 23 Dec 2013 15:54:17 +1100 [thread overview]
Message-ID: <20131223155417.99a66c575143e25d36232a77@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpio/gpio-sch311x.c: In function 'sch311x_sio_enter':
drivers/gpio/gpio-sch311x.c:115:2: error: implicit declaration of function 'outb' [-Werror=implicit-function-declaration]
outb(SIO_CONFIG_KEY_ENTER, sio_config_port);
^
drivers/gpio/gpio-sch311x.c: In function 'sch311x_sio_inb':
drivers/gpio/gpio-sch311x.c:128:2: error: implicit declaration of function 'inb' [-Werror=implicit-function-declaration]
return inb(sio_config_port + 1);
^
Caused by commit 12262bef8f46 ("gpio: add GPIO support for SMSC SCH311x")
from the gpio tree.
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:[~2013-12-23 4:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 4:54 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-05 6:35 linux-next: build failure after merge of the final tree (gpio tree related) Stephen Rothwell
2014-03-05 7:16 ` Linus Walleij
2014-03-05 16:42 ` Fabian Vogt
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=20131223155417.99a66c575143e25d36232a77@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=br1@einfach.org \
--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).