From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 2/3] drivers/mfd: rpisense: Raspberry Pi senseHAT joystick driver
Date: Sun, 08 Aug 2021 03:06:08 +0800 [thread overview]
Message-ID: <202108080236.RtKXrkrY-lkp@intel.com> (raw)
In-Reply-To: <20210807002722.2634585-3-jsavitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
Hi Joel,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on lee-mfd/for-mfd-next]
[also build test ERROR on linux/master linus/master v5.14-rc4 next-20210806]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Joel-Savitz/Raspberry-Pi-Sense-HAT-driver/20210807-082859
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: mips-buildonly-randconfig-r004-20210808 (attached as .config)
compiler: mips64-linux-gcc (GCC) 10.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
# https://github.com/0day-ci/linux/commit/3de478e79fa7f81e0d89102c8b557981506495ff
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Joel-Savitz/Raspberry-Pi-Sense-HAT-driver/20210807-082859
git checkout 3de478e79fa7f81e0d89102c8b557981506495ff
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=mips SHELL=/bin/bash
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 >>):
mips64-linux-ld: drivers/mfd/rpisense-js.o: in function `rpisense_js_report':
>> rpisense-js.c:(.text.rpisense_js_report+0xac): undefined reference to `input_event'
>> mips64-linux-ld: rpisense-js.c:(.text.rpisense_js_report+0xcc): undefined reference to `input_event'
mips64-linux-ld: drivers/mfd/rpisense-js.o: in function `rpisense_js_probe':
>> rpisense-js.c:(.text.rpisense_js_probe+0x68): undefined reference to `devm_input_allocate_device'
>> mips64-linux-ld: rpisense-js.c:(.text.rpisense_js_probe+0x158): undefined reference to `input_register_device'
---
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: 27235 bytes --]
next prev parent reply other threads:[~2021-08-07 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 0:27 [RFC PATCH 0/3] Raspberry Pi Sense HAT driver Joel Savitz
2021-08-07 0:27 ` [RFC PATCH 1/3] drivers/mfd: rpisense: Raspberry Pi senseHAT core driver Joel Savitz
2021-08-07 0:32 ` Randy Dunlap
2021-08-07 9:53 ` Stefan Wahren
2021-08-07 0:27 ` [RFC PATCH 2/3] drivers/mfd: rpisense: Raspberry Pi senseHAT joystick driver Joel Savitz
2021-08-07 13:05 ` Peter Robinson
2021-08-07 19:06 ` kernel test robot [this message]
2021-08-07 0:27 ` [RFC PATCH 3/3] drivers/mfd: rpisense: Raspberry Pi senseHAT 8x8 LED matrix display driver Joel Savitz
2021-08-07 13:20 ` Peter Robinson
2021-08-07 9:03 ` [RFC PATCH 0/3] Raspberry Pi Sense HAT driver Stefan Wahren
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=202108080236.RtKXrkrY-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.