From: kernel test robot <lkp@intel.com>
To: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, herbert@gondor.apana.org.au,
robh@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
krzk+dt@kernel.org, conor+dt@kernel.org,
Ruud.Derwig@synopsys.com, manjunath.hadli@vayavyalabs.com,
adityak@vayavyalabs.com,
Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v6 4/4] Add SPAcc Kconfig and Makefile
Date: Sat, 4 Oct 2025 09:18:53 +0800 [thread overview]
Message-ID: <202510040852.qK4TiL4k-lkp@intel.com> (raw)
In-Reply-To: <20250929074334.118413-5-pavitrakumarm@vayavyalabs.com>
Hi Pavitrakumar,
kernel test robot noticed the following build errors:
[auto build test ERROR on 166c83f7789ed02dc1f25bc7bed4a1beb25343aa]
url: https://github.com/intel-lab-lkp/linux/commits/Pavitrakumar-Managutte/dt-bindings-crypto-Document-support-for-SPAcc/20250929-155434
base: 166c83f7789ed02dc1f25bc7bed4a1beb25343aa
patch link: https://lore.kernel.org/r/20250929074334.118413-5-pavitrakumarm%40vayavyalabs.com
patch subject: [PATCH v6 4/4] Add SPAcc Kconfig and Makefile
config: i386-randconfig-013-20251004 (https://download.01.org/0day-ci/archive/20251004/202510040852.qK4TiL4k-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251004/202510040852.qK4TiL4k-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/202510040852.qK4TiL4k-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: crypto_engine_alloc_init
>>> referenced by spacc_device.c:88 (drivers/crypto/dwc-spacc/spacc_device.c:88)
>>> drivers/crypto/dwc-spacc/spacc_device.o:(spacc_crypto_probe) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: crypto_engine_start
>>> referenced by spacc_device.c:95 (drivers/crypto/dwc-spacc/spacc_device.c:95)
>>> drivers/crypto/dwc-spacc/spacc_device.o:(spacc_crypto_probe) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: crypto_engine_stop
>>> referenced by spacc_device.c:203 (drivers/crypto/dwc-spacc/spacc_device.c:203)
>>> drivers/crypto/dwc-spacc/spacc_device.o:(spacc_crypto_probe) in archive vmlinux.a
>>> referenced by spacc_device.c:250 (drivers/crypto/dwc-spacc/spacc_device.c:250)
>>> drivers/crypto/dwc-spacc/spacc_device.o:(spacc_crypto_remove) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: crypto_engine_exit
>>> referenced by spacc_device.c:206 (drivers/crypto/dwc-spacc/spacc_device.c:206)
>>> drivers/crypto/dwc-spacc/spacc_device.o:(spacc_crypto_probe) in archive vmlinux.a
>>> referenced by spacc_device.c:251 (drivers/crypto/dwc-spacc/spacc_device.c:251)
>>> drivers/crypto/dwc-spacc/spacc_device.o:(spacc_crypto_remove) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-10-04 1:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 7:43 [PATCH v6 0/4] Add SPAcc Crypto Driver Pavitrakumar Managutte
2025-09-29 7:43 ` [PATCH v6 1/4] dt-bindings: crypto: Document support for SPAcc Pavitrakumar Managutte
2025-09-29 7:43 ` [PATCH v6 2/4] Add SPAcc ahash support Pavitrakumar Managutte
2025-09-29 7:43 ` [PATCH v6 3/4] Add SPAcc AUTODETECT Support Pavitrakumar Managutte
2025-09-29 7:43 ` [PATCH v6 4/4] Add SPAcc Kconfig and Makefile Pavitrakumar Managutte
2025-10-04 1:18 ` kernel test robot [this message]
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=202510040852.qK4TiL4k-lkp@intel.com \
--to=lkp@intel.com \
--cc=Ruud.Derwig@synopsys.com \
--cc=adityak@vayavyalabs.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=manjunath.hadli@vayavyalabs.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavitrakumarm@vayavyalabs.com \
--cc=robh@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).