From: kernel test robot <lkp@intel.com>
To: Feng Chen <feng.chen@amlogic.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Xianwei Zhao <xianwei.zhao@amlogic.com>
Subject: alpha-linux-ld: drivers/spi/spi-amlogic-spifc-a4.c:289:undefined reference to `__ffsdi2'
Date: Wed, 15 Oct 2025 15:08:57 +0800 [thread overview]
Message-ID: <202510151522.iQuRChZM-lkp@intel.com> (raw)
Hi Feng,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 9b332cece987ee1790b2ed4c989e28162fa47860
commit: 4670db6f32e9379f5ab6c9bb2a6787cd9b9230a9 spi: amlogic: add driver for Amlogic SPI Flash Controller
date: 5 weeks ago
config: alpha-randconfig-r123-20251014 (https://download.01.org/0day-ci/archive/20251015/202510151522.iQuRChZM-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251015/202510151522.iQuRChZM-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/202510151522.iQuRChZM-lkp@intel.com/
All errors (new ones prefixed by >>):
`xe_configfs_exit' referenced in section `.data.rel.ro' of drivers/gpu/drm/xe/xe_module.o: defined in discarded section `.exit.text' of drivers/gpu/drm/xe/xe_configfs.o
alpha-linux-ld: drivers/spi/spi-amlogic-spifc-a4.o: in function `aml_sfc_set_bus_width':
drivers/spi/spi-amlogic-spifc-a4.c:289:(.text+0x5ec): undefined reference to `__ffsdi2'
>> alpha-linux-ld: drivers/spi/spi-amlogic-spifc-a4.c:289:(.text+0x5f0): undefined reference to `__ffsdi2'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-15 7:09 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=202510151522.iQuRChZM-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=feng.chen@amlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=xianwei.zhao@amlogic.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
all inboxes | Powered by JetHome®