From: kernel test robot <lkp@intel.com>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>
Subject: ld.lld: error: undefined symbol: firmware_upload_register
Date: Thu, 6 Jul 2023 07:43:13 +0800 [thread overview]
Message-ID: <202307060742.vdkvv1Z3-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 73a3fcdaa73200e38e38f7e8a32c9b901c5b95b5
commit: 9521875bbe0055805557fff0b08fd9a29d02b7bc cxl: add a firmware update mechanism using the sysfs firmware loader
date: 10 days ago
config: x86_64-randconfig-x016-20230706 (https://download.01.org/0day-ci/archive/20230706/202307060742.vdkvv1Z3-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230706/202307060742.vdkvv1Z3-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/202307060742.vdkvv1Z3-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: firmware_upload_register
>>> referenced by memdev.c:836 (drivers/cxl/core/memdev.c:836)
>>> drivers/cxl/core/memdev.o:(cxl_memdev_setup_fw_upload) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: firmware_upload_unregister
>>> referenced by memdev.c:824 (drivers/cxl/core/memdev.c:824)
>>> drivers/cxl/core/memdev.o:(cxl_memdev_setup_fw_upload) in archive vmlinux.a
>>> referenced by memdev.c:824 (drivers/cxl/core/memdev.c:824)
>>> drivers/cxl/core/memdev.o:(devm_cxl_remove_fw_upload) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-07-05 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 23:43 kernel test robot [this message]
2023-07-06 1:17 ` ld.lld: error: undefined symbol: firmware_upload_register Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2022-11-09 12:30 kernel test robot
2022-11-11 21:59 ` Randy Dunlap
2022-11-14 19:49 ` Russ Weight
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=202307060742.vdkvv1Z3-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vishal.l.verma@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