From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: [linux-next:master 3893/10295] undefined reference to `auxiliary_device_init'
Date: Sat, 23 Dec 2023 09:03:43 +0800 [thread overview]
Message-ID: <202312230924.iWMeUsyr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 39676dfe52331dba909c617f213fdb21015c8d10
commit: 7d9f1b72b29698e3030c2b163522cf4aa91b47e9 [3893/10295] usb: typec: qcom-pmic-typec: switch to DRM_AUX_HPD_BRIDGE
config: x86_64-buildonly-randconfig-001-20231222 (https://download.01.org/0day-ci/archive/20231223/202312230924.iWMeUsyr-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231223/202312230924.iWMeUsyr-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312230924.iWMeUsyr-lkp@intel.com/
Note: the linux-next/master HEAD 39676dfe52331dba909c617f213fdb21015c8d10 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
ld: vmlinux.o: in function `drm_dp_hpd_bridge_register':
>> (.text+0x13d3030): undefined reference to `auxiliary_device_init'
>> ld: (.text+0x13d3046): undefined reference to `__auxiliary_device_add'
ld: vmlinux.o: in function `drm_aux_hpd_bridge_drv_init':
>> aux-hpd-bridge.c:(.init.text+0x7feda): undefined reference to `__auxiliary_driver_register'
ld: vmlinux.o: in function `drm_aux_hpd_bridge_drv_exit':
>> aux-hpd-bridge.c:(.exit.text+0xa58c): undefined reference to `auxiliary_driver_unregister'
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for DRM_AUX_HPD_BRIDGE
Depends on [n]: HAS_IOMEM [=y] && DRM_BRIDGE [=y] && OF [=n]
Selected by [y]:
- TYPEC_QCOM_PMIC [=y] && USB_SUPPORT [=y] && TYPEC [=y] && TYPEC_TCPM [=y] && (ARCH_QCOM || COMPILE_TEST [=y]) && (DRM [=y] || DRM [=y]=n) && DRM_BRIDGE [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-23 1:07 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=202312230924.iWMeUsyr-lkp@intel.com \
--to=lkp@intel.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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