From: kernel test robot <lkp@intel.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] crypto: x86/aes-ctr - rewrite AES-NI optimized CTR and add VAES support
Date: Thu, 30 Jan 2025 04:10:21 +0800 [thread overview]
Message-ID: <202501300300.GpVBw7ZQ-lkp@intel.com> (raw)
In-Reply-To: <20250128063118.187690-1-ebiggers@kernel.org>
Hi Eric,
kernel test robot noticed the following build errors:
[auto build test ERROR on 805ba04cb7ccfc7d72e834ebd796e043142156ba]
url: https://github.com/intel-lab-lkp/linux/commits/Eric-Biggers/crypto-x86-aes-ctr-rewrite-AES-NI-optimized-CTR-and-add-VAES-support/20250128-143541
base: 805ba04cb7ccfc7d72e834ebd796e043142156ba
patch link: https://lore.kernel.org/r/20250128063118.187690-1-ebiggers%40kernel.org
patch subject: [PATCH] crypto: x86/aes-ctr - rewrite AES-NI optimized CTR and add VAES support
config: x86_64-randconfig-072-20250129 (https://download.01.org/0day-ci/archive/20250130/202501300300.GpVBw7ZQ-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250130/202501300300.GpVBw7ZQ-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/202501300300.GpVBw7ZQ-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
WARNING: modpost: missing MODULE_DESCRIPTION() in lib/ucs2_string.o
>> ERROR: modpost: "nil" [arch/x86/crypto/aesni-intel.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-01-29 20:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250128063118.187690-1-ebiggers@kernel.org>]
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=202501300300.GpVBw7ZQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=ebiggers@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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