From: kernel test robot <lkp@intel.com>
To: Sven Peter <sven@svenpeter.dev>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [asahilinux:sven/atcphy 30/31] ld.lld: error: undefined symbol: drm_connector_oob_hotplug_event
Date: Sun, 18 May 2025 10:56:53 +0800 [thread overview]
Message-ID: <202505181048.9drFn91S-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux sven/atcphy
head: bb58cc6399a58218b8b5204a9fadf26f07c7f0f3
commit: 10afb98e90699baea02c783a19381cb8b81c6af8 [30/31] usb: typec: tipd: Forward DP hotplug events to DRM
config: arm-randconfig-002-20250518 (https://download.01.org/0day-ci/archive/20250518/202505181048.9drFn91S-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250518/202505181048.9drFn91S-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/202505181048.9drFn91S-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: drm_connector_oob_hotplug_event
>>> referenced by core.c
>>> drivers/usb/typec/tipd/core.o:(cd321x_update_work) in archive vmlinux.a
>>> referenced by core.c
>>> drivers/usb/typec/tipd/core.o:(cd321x_update_work) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-05-18 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 2:56 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-30 8:28 [asahilinux:sven/atcphy 30/31] ld.lld: error: undefined symbol: drm_connector_oob_hotplug_event kernel test robot
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=202505181048.9drFn91S-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sven@svenpeter.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