From: kbuild test robot <lkp@intel.com>
To: Parthiban Nallathambi <pn@denx.de>
Cc: kbuild-all@01.org, jic23@kernel.org, knaack.h@gmx.de,
lars@metafoo.de, pmeerw@pmeerw.net, robh+dt@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
matthias.bgg@gmail.com, wd@denx.de, sbabic@denx.de, hs@denx.de,
Parthiban Nallathambi <pn@denx.de>
Subject: Re: [PATCH v2 1/2] iio: light: Add support for vishay vcnl4035
Date: Sat, 30 Jun 2018 07:46:24 +0800 [thread overview]
Message-ID: <201806300731.TzGYMxwW%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180629153802.1639514-1-pn@denx.de>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
Hi Parthiban,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on v4.18-rc2 next-20180629]
[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/Parthiban-Nallathambi/iio-light-Add-support-for-vishay-vcnl4035/20180630-021705
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=8.1.0 make.cross ARCH=ia64
All errors (new ones prefixed by >>):
ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined!
ERROR: "__sw_hweight8" [drivers/net/wireless/mediatek/mt76/mt76.ko] undefined!
ERROR: "ia64_delay_loop" [drivers/net/phy/mdio-cavium.ko] undefined!
>> ERROR: "__sw_hweight8" [drivers/iio/light/vcnl4035.ko] undefined!
---
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: 50877 bytes --]
next prev parent reply other threads:[~2018-06-29 23:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 12:30 [PATCH " Parthiban Nallathambi
2018-06-28 12:30 ` [PATCH 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-06-28 15:35 ` [PATCH 1/2] iio: light: Add support " kbuild test robot
2018-06-29 15:38 ` [PATCH v2 " Parthiban Nallathambi
2018-06-29 15:38 ` [PATCH v2 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-07-06 20:34 ` Rob Herring
2018-07-07 17:06 ` Parthiban Nallathambi
2018-06-29 23:46 ` kbuild test robot [this message]
2018-06-30 9:51 ` [PATCH v2 1/2] iio: light: Add support " Peter Meerwald-Stadler
2018-07-03 12:58 ` Parthiban Nallathambi
2018-08-02 9:52 ` [PATCH v3 " Parthiban Nallathambi
2018-08-02 9:52 ` [PATCH v3 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-08-02 12:51 ` Jonathan Cameron
2018-08-02 12:49 ` [PATCH v3 1/2] iio: light: Add support " Jonathan Cameron
2018-08-02 14:01 ` Parthiban Nallathambi
2018-08-03 22:16 ` Jonathan Cameron
2018-06-29 17:59 ` [PATCH " Jonathan Cameron
2018-07-03 13:35 ` Parthiban Nallathambi
2018-07-07 16:23 ` Jonathan Cameron
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=201806300731.TzGYMxwW%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=hs@denx.de \
--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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=pn@denx.de \
--cc=robh+dt@kernel.org \
--cc=sbabic@denx.de \
--cc=wd@denx.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®