From: kbuild test robot <lkp@intel.com>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: kbuild-all@01.org, lee.jones@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org, broonie@kernel.org, linus.walleij@linaro.org,
robh+dt@kernel.org, mark.rutland@arm.com, lgirdwood@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 1/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar
Date: Fri, 7 Sep 2018 08:06:52 +0800 [thread overview]
Message-ID: <201809070844.CGeY6FIt%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180905104120.17252-1-ckeepax@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hi Charles,
I love your patch! Yet something to improve:
[auto build test ERROR on ljones-mfd/for-mfd-next]
[also build test ERROR on v4.19-rc2 next-20180906]
[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/Charles-Keepax/mfd-lochnagar-Add-support-for-the-Cirrus-Logic-Lochnagar/20180907-010308
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: alpha-allmodconfig (attached as .config)
compiler: alpha-linux-gnu-gcc (Debian 7.2.0-11) 7.2.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=7.2.0 make.cross ARCH=alpha
All errors (new ones prefixed by >>):
drivers/mfd/lochnagar-i2c.o: In function `lochnagar_i2c_probe':
>> (.text+0x4ec): undefined reference to `__devm_regmap_init_i2c'
(.text+0x500): undefined reference to `__devm_regmap_init_i2c'
drivers/mfd/lochnagar-i2c.o: In function `lochnagar_i2c_init':
>> (.init.text+0x10): undefined reference to `i2c_register_driver'
(.init.text+0x24): undefined reference to `i2c_register_driver'
---
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: 53401 bytes --]
next prev parent reply other threads:[~2018-09-07 0:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 10:41 [PATCH 1/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar Charles Keepax
2018-09-05 10:41 ` [PATCH 2/5] clk: " Charles Keepax
2018-09-05 10:41 ` [PATCH 3/5] regulator: " Charles Keepax
2018-09-05 10:41 ` [PATCH 4/5] pinctrl: " Charles Keepax
2018-09-25 20:20 ` Rob Herring
2018-09-05 10:41 ` [PATCH 5/5] mfd: lochnagar: Add initial binding documentation Charles Keepax
2018-09-05 11:01 ` [PATCH 1/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar Mark Brown
2018-09-06 13:46 ` Linus Walleij
2018-09-06 14:48 ` Charles Keepax
[not found] ` <5b9f3f61.1c69fb81.f4e64.f592@mx.google.com>
2018-09-17 13:50 ` Charles Keepax
2018-09-07 0:06 ` kbuild test robot [this message]
2018-09-07 8:44 ` Charles Keepax
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=201809070844.CGeY6FIt%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=patches@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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