From: Wolfram Sang <wsa@the-dreams.de>
To: Shawn Guo <shawnguo@kernel.org>
Cc: linux-i2c@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH] i2c: zx2967: drop COMPILE_TEST dependency
Date: Tue, 27 Jun 2017 21:59:05 +0200 [thread overview]
Message-ID: <20170627195905.zpirzdx7f22dj4ww@ninjato> (raw)
In-Reply-To: <1498314326-16121-1-git-send-email-shawnguo@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Sat, Jun 24, 2017 at 10:25:26PM +0800, Shawn Guo wrote:
> From: Shawn Guo <shawn.guo@linaro.org>
>
> 0-DAY kernel test reports the following build issue on IA64 architecture
> with allmodconfig.
>
> drivers/i2c/busses/i2c-zx2967.c: In function 'zx2967_i2c_writesb':
> >> drivers/i2c/busses/i2c-zx2967.c:87:2: error: implicit declaration of function 'writesb' [-Werror=implicit-function-declaration]
> writesb(i2c->reg_base + reg, data, len);
> ^~~~~~~
> drivers/i2c/busses/i2c-zx2967.c: In function 'zx2967_i2c_readsb':
> >> drivers/i2c/busses/i2c-zx2967.c:93:2: error: implicit declaration of function 'readsb' [-Werror=implicit-function-declaration]
> readsb(i2c->reg_base + reg, data, len);
> ^~~~~~
> cc1: some warnings being treated as errors
>
> It's caused by that writesb/readsb are unavailable on IA64 architecture.
> Let's drop COMPILE_TEST dependency to avoid the build issue.
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-06-27 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 14:25 [PATCH] i2c: zx2967: drop COMPILE_TEST dependency Shawn Guo
2017-06-27 19:59 ` Wolfram Sang [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=20170627195905.zpirzdx7f22dj4ww@ninjato \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=shawnguo@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