From: Wolfram Sang <wsa@the-dreams.de>
To: Shawn Guo <shawnguo@kernel.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
Baoyou Xie <baoyou.xie@linaro.org>,
kbuild-all@01.org, linux-i2c@vger.kernel.org,
Wolfram Sang <wsa-dev@sang-engineering.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Jun Nie <jun.nie@linaro.org>
Subject: Re: [wsa:i2c/for-next 42/44] drivers/i2c/busses/i2c-zx2967.c:87:2: error: implicit declaration of function 'writesb'
Date: Sat, 24 Jun 2017 16:15:00 +0200 [thread overview]
Message-ID: <20170624141500.GA1566@katana> (raw)
In-Reply-To: <20170624135754.GD23753@dragon>
[-- Attachment #1: Type: text/plain, Size: 167 bytes --]
> I think what we should do is dropping COMPILE_TEST or adding !IA64
> dependency. @Wolfram, what do you think?
Let's drop COMPILE_TEST for now, I'd say.
Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-24 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 20:50 [wsa:i2c/for-next 42/44] drivers/i2c/busses/i2c-zx2967.c:87:2: error: implicit declaration of function 'writesb' kbuild test robot
2017-06-24 13:57 ` Shawn Guo
2017-06-24 14:15 ` Wolfram Sang [this message]
2017-06-24 14:26 ` Shawn Guo
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=20170624141500.GA1566@katana \
--to=wsa@the-dreams.de \
--cc=andy.shevchenko@gmail.com \
--cc=baoyou.xie@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=jun.nie@linaro.org \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=wsa-dev@sang-engineering.com \
/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.