From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [pza:imx-drm/next 9/24] dw_hdmi-imx.c:undefined reference to `of_drm_find_bridge'
Date: Sat, 09 Jan 2021 20:18:04 +0800 [thread overview]
Message-ID: <202101092016.C33DZYfM-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
tree: https://git.pengutronix.de/git/pza/linux imx-drm/next
head: 82581fcf070b68a91fb3a3ade08d9a76380a4789
commit: c805ec7eb21034008da764e9401f791f6ea86506 [9/24] drm/imx: dw_hdmi-imx: move initialization into probe
config: mips-randconfig-r015-20210108 (attached as .config)
compiler: mips-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 remote add pza https://git.pengutronix.de/git/pza/linux
git fetch --no-tags pza imx-drm/next
git checkout c805ec7eb21034008da764e9401f791f6ea86506
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the pza/imx-drm/next HEAD 82581fcf070b68a91fb3a3ade08d9a76380a4789 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
mips-linux-ld: drivers/gpu/drm/imx/dw_hdmi-imx.o: in function `dw_hdmi_imx_probe':
>> dw_hdmi-imx.c:(.text+0x2c0): undefined reference to `of_drm_find_bridge'
---
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: 27739 bytes --]
reply other threads:[~2021-01-09 12:18 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=202101092016.C33DZYfM-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.