From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [afaerber:rtd1295-next 99/166] g2227.c:undefined reference to `i2c_register_driver'
Date: Sun, 14 Jun 2020 14:23:35 +0800 [thread overview]
Message-ID: <202006141432.btPYmoJC%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
tree: https://github.com/afaerber/linux.git rtd1295-next
head: af9d43a7ab49361eb3297bfc219db99e3ced1bb1
commit: 3b369dfc364fc8a7f6a4a4fbcb2c7c8f6d7e6880 [99/166] regulator: Add GMT G2227 driver
config: h8300-allmodconfig (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 3b369dfc364fc8a7f6a4a4fbcb2c7c8f6d7e6880
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
h8300-linux-ld: drivers/regulator/g2227.o: in function `g2227_probe':
g2227.c:(.text+0x87): undefined reference to `__devm_regmap_init_i2c'
h8300-linux-ld: drivers/regulator/g2227.o: in function `g2227_driver_init':
>> g2227.c:(.init.text+0xf): undefined reference to `i2c_register_driver'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 55253 bytes --]
reply other threads:[~2020-06-14 6:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202006141432.btPYmoJC%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.