From: kernel test robot <lkp@intel.com>
To: Wei Fang <wei.fang@nxp.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jakub Kicinski <kuba@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: [linux-next:master 8543/12618] ld.lld: error: undefined symbol: ntmp_init_cbdr
Date: Thu, 22 May 2025 07:40:27 +0800 [thread overview]
Message-ID: <202505220734.x6TF6oHR-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 7bac2c97af4078d7a627500c9bcdd5b033f97718
commit: e3f4a0a8ddb41962efa51c6353e869b90d183e68 [8543/12618] net: enetc: add command BD ring support for i.MX95 ENETC
config: arm-randconfig-002-20250522 (https://download.01.org/0day-ci/archive/20250522/202505220734.x6TF6oHR-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/20250522/202505220734.x6TF6oHR-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/202505220734.x6TF6oHR-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: ntmp_init_cbdr
>>> referenced by enetc_cbdr.c:88 (drivers/net/ethernet/freescale/enetc/enetc_cbdr.c:88)
>>> drivers/net/ethernet/freescale/enetc/enetc_cbdr.o:(enetc4_setup_cbdr) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: ntmp_free_cbdr
>>> referenced by enetc_cbdr.c:96 (drivers/net/ethernet/freescale/enetc/enetc_cbdr.c:96)
>>> drivers/net/ethernet/freescale/enetc/enetc_cbdr.o:(enetc4_teardown_cbdr) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-21 23:41 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=202505220734.x6TF6oHR-lkp@intel.com \
--to=lkp@intel.com \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.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