From: kernel test robot <lkp@intel.com>
To: Alexey Makhalov <alexey.makhalov@broadcom.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: [tip:x86/vmware 4/8] ld.lld: error: undefined symbol: vmware_hypercall_slow
Date: Sat, 15 Jun 2024 21:22:00 +0800 [thread overview]
Message-ID: <202406152101.ioasijN1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/vmware
head: ef08e7dc21307b226b5280d5e8cfea687bfd2866
commit: e5ac9008b79c59235c34494e555419665022f5e1 [4/8] drm/vmwgfx: Use VMware hypercall API
config: i386-buildonly-randconfig-001-20240615 (https://download.01.org/0day-ci/archive/20240615/202406152101.ioasijN1-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240615/202406152101.ioasijN1-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/202406152101.ioasijN1-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: vmware_hypercall_slow
>>> referenced by vmwgfx_msg.c
>>> drivers/gpu/drm/vmwgfx/vmwgfx_msg.o:(vmw_host_get_guestinfo) in archive vmlinux.a
>>> referenced by vmwgfx_msg.c
>>> drivers/gpu/drm/vmwgfx/vmwgfx_msg.o:(vmw_host_get_guestinfo) in archive vmlinux.a
>>> referenced by vmwgfx_msg.c
>>> drivers/gpu/drm/vmwgfx/vmwgfx_msg.o:(vmw_send_msg) in archive vmlinux.a
>>> referenced 13 more times
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-15 13:22 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=202406152101.ioasijN1-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexey.makhalov@broadcom.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).