From: Baolin Wang <baolin.wang@linaro.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Baolin Wang <baolin.wang@spreadtrum.com>,
kbuild-all@01.org, linux-i2c@vger.kernel.org,
Wolfram Sang <wsa-dev@sang-engineering.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [wsa:i2c/for-next 65/74] i2c-sprd.c:undefined reference to `i2c_del_adapter'
Date: Wed, 30 Aug 2017 11:07:45 +0800 [thread overview]
Message-ID: <CAMz4kuKBnw00WCbDa3KU3b9OchX5bHZzKYNMCdiSmNZvZ5d5sw@mail.gmail.com> (raw)
In-Reply-To: <201708301003.pzfftflw%fengguang.wu@intel.com>
Hi,
On 30 August 2017 at 10:24, kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
> head: 60999e2bb4ed42743b81d718521deccdb8888335
> commit: 8b9ec0719834fe66146d138d62ed66cef025c864 [65/74] i2c: Add Spreadtrum I2C controller driver
> config: arm64-allmodconfig (attached as .config)
> compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 8b9ec0719834fe66146d138d62ed66cef025c864
> # save the attached .config to linux build tree
> make.cross ARCH=arm64
>
> All errors (new ones prefixed by >>):
>
> drivers/i2c/busses/i2c-sprd.o: In function `sprd_i2c_remove':
>>> i2c-sprd.c:(.text+0x168): undefined reference to `i2c_del_adapter'
> drivers/i2c/busses/i2c-sprd.o: In function `sprd_i2c_probe':
>>> i2c-sprd.c:(.text+0x1400): undefined reference to `i2c_add_numbered_adapter'
I realized Spreadtrum I2C driver can not be build as module, so it
should depend on I2C=y. Since Wolfram had applied this patch series, I
will send one patch to fix this build error. Thanks.
--
Baolin.wang
Best Regards
prev parent reply other threads:[~2017-08-30 3:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 2:24 [wsa:i2c/for-next 65/74] i2c-sprd.c:undefined reference to `i2c_del_adapter' kbuild test robot
2017-08-30 3:07 ` Baolin Wang [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=CAMz4kuKBnw00WCbDa3KU3b9OchX5bHZzKYNMCdiSmNZvZ5d5sw@mail.gmail.com \
--to=baolin.wang@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=baolin.wang@spreadtrum.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.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 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).