From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [chrome-os:chromeos-5.10 17159/17821] arm-linux-gnueabi-ld: drivers/video/fbdev/simplefb.o:undefined reference to `cfb_fillrect'
Date: Sun, 25 Jul 2021 08:15:45 +0800 [thread overview]
Message-ID: <202107250840.0aGhEQtF-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.10
head: 370c019298b937a0e4f65756f8297af5194a41db
commit: 95e15e098b0dd8fcdfcb42abd1e5fd22d06311f7 [17159/17821] UPSTREAM: drm: Add simpledrm driver
config: arm-randconfig-r005-20210725 (attached as .config)
compiler: arm-linux-gnueabi-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
git remote add chrome-os https://chromium.googlesource.com/chromiumos/third_party/kernel
git fetch --no-tags chrome-os chromeos-5.10
git checkout 95e15e098b0dd8fcdfcb42abd1e5fd22d06311f7
# 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=arm 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 >>):
>> arm-linux-gnueabi-ld: drivers/video/fbdev/simplefb.o:(.rodata+0x3c): undefined reference to `cfb_fillrect'
>> arm-linux-gnueabi-ld: drivers/video/fbdev/simplefb.o:(.rodata+0x40): undefined reference to `cfb_copyarea'
>> arm-linux-gnueabi-ld: drivers/video/fbdev/simplefb.o:(.rodata+0x44): undefined reference to `cfb_imageblit'
---
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: 28100 bytes --]
reply other threads:[~2021-07-25 0:15 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=202107250840.0aGhEQtF-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.