From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: kbuild-all@lists.01.org,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: [nomadik:ux500-skomer-v5.11-rc1 6/7] leds-rt8515.c:undefined reference to `v4l2_flash_release'
Date: Tue, 29 Dec 2020 08:23:34 +0800 [thread overview]
Message-ID: <202012290827.Ra3zdjz5-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git ux500-skomer-v5.11-rc1
head: 9576d8e150530c5a4f2258e60c94f3dd1fd0c7ff
commit: c35889819d0b03a28de38227f772bb74922d7fc2 [6/7] leds: rt8515: Add Richtek RT8515 LED driver
config: nios2-randconfig-c003-20201228 (attached as .config)
compiler: nios2-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
# https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git/commit/?id=c35889819d0b03a28de38227f772bb74922d7fc2
git remote add nomadik https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git
git fetch --no-tags nomadik ux500-skomer-v5.11-rc1
git checkout c35889819d0b03a28de38227f772bb74922d7fc2
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=nios2
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 >>):
nios2-linux-ld: drivers/leds/flash/leds-rt8515.o: in function `rt8515_remove':
>> leds-rt8515.c:(.text+0x30): undefined reference to `v4l2_flash_release'
leds-rt8515.c:(.text+0x30): relocation truncated to fit: R_NIOS2_CALL26 against `v4l2_flash_release'
nios2-linux-ld: drivers/leds/flash/leds-rt8515.o: in function `rt8515_probe':
>> leds-rt8515.c:(.text+0x5a8): undefined reference to `v4l2_flash_init'
leds-rt8515.c:(.text+0x5a8): relocation truncated to fit: R_NIOS2_CALL26 against `v4l2_flash_init'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35725 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-12-29 0:26 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=202012290827.Ra3zdjz5-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sakari.ailus@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).