From: kbuild test robot <lkp@intel.com>
To: Pierre Bourdon <delroth@google.com>
Cc: kbuild-all@01.org, Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Pierre Bourdon <delroth@google.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: light: add driver for bh1730fvc chips
Date: Fri, 23 Feb 2018 15:56:50 +0800 [thread overview]
Message-ID: <201802231535.ER0ua4Vk%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180221125512.8265-1-delroth@google.com>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
Hi Pierre,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on v4.16-rc2 next-20180222]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Pierre-Bourdon/iio-light-add-driver-for-bh1730fvc-chips/20180222-064336
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/iio/light/bh1730.o: In function `bh1730_read_raw':
>> bh1730.c:(.text+0x31d): undefined reference to `__udivdi3'
bh1730.c:(.text+0x37d): undefined reference to `__udivdi3'
bh1730.c:(.text+0x38a): undefined reference to `__udivdi3'
>> bh1730.c:(.text+0x3a4): undefined reference to `__divdi3'
>> bh1730.c:(.text+0x3b8): undefined reference to `__moddi3'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 61829 bytes --]
prev parent reply other threads:[~2018-02-23 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 12:55 Pierre Bourdon
2018-02-21 15:31 ` Daniel Baluta
2018-02-21 16:15 ` Pierre Bourdon (delroth)
2018-02-21 18:32 ` Daniel Baluta
2018-02-21 19:45 ` [PATCH v2 1/2] " Pierre Bourdon
2018-02-21 19:45 ` [PATCH v2 2/2] dt-bindings: iio: light: Add bh1730fvc bindings Pierre Bourdon
2018-02-21 21:57 ` [PATCH v2 1/2] iio: light: add driver for bh1730fvc chips Andy Shevchenko
2018-02-22 14:58 ` Pierre Bourdon (delroth)
2018-02-24 12:41 ` Jonathan Cameron
2018-02-24 12:53 ` Jonathan Cameron
2018-02-23 7:56 ` kbuild test robot [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=201802231535.ER0ua4Vk%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=delroth@google.com \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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®