From: Mark Brown <broonie@kernel.org>
To: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>,
Wolfram Sang <wsa@the-dreams.de>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: master build: 2 failures 15 warnings (v4.0-5833-g6c373ca89399)
Date: Wed, 15 Apr 2015 19:08:25 +0100 [thread overview]
Message-ID: <20150415180824.GT6023@sirena.org.uk> (raw)
In-Reply-To: <E1YiR8T-0003Hq-6F@debutante>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Wed, Apr 15, 2015 at 06:30:01PM +0100, Build bot for Mark Brown wrote:
For the past couple of days -next has been failing to build on both arm
and arm64 with:
> arm64-allmodconfig
> ../drivers/i2c/busses/i2c-jz4780.c:181:2: error: implicit declaration of function 'readw' [-Werror=implicit-function-declaration]
> ../drivers/i2c/busses/i2c-jz4780.c:187:2: error: implicit declaration of function 'writew' [-Werror=implicit-function-declaration]
>
> arm-allmodconfig
> ../drivers/i2c/busses/i2c-jz4780.c:181:2: error: implicit declaration of function 'readw' [-Werror=implicit-function-declaration]
> ../drivers/i2c/busses/i2c-jz4780.c:187:2: error: implicit declaration of function 'writew' [-Werror=implicit-function-declaration]
due to relying on an implicit inclusion of asm/io.h. This now also
affects Linus' tree. I've sent a patch.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next parent reply other threads:[~2015-04-15 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YiR8T-0003Hq-6F@debutante>
2015-04-15 18:08 ` Mark Brown [this message]
2015-04-15 18:59 ` Wolfram Sang
2015-04-15 19:01 ` 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=20150415180824.GT6023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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
all inboxes | Powered by JetHome®