From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [PATCH v5 4/8] crypto: x86/aesni-xctr: Add accelerated implementation of XCTR
Date: Wed, 27 Apr 2022 17:56:39 +0800 [thread overview]
Message-ID: <202204271747.9NI6Iyxe-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3144 bytes --]
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
In-Reply-To: <20220427003759.1115361-5-nhuck@google.com>
References: <20220427003759.1115361-5-nhuck@google.com>
TO: Nathan Huckleberry <nhuck@google.com>
Hi Nathan,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on herbert-cryptodev-2.6/master]
[also build test WARNING on herbert-crypto-2.6/master linus/master v5.18-rc4 next-20220427]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/intel-lab-lkp/linux/commits/Nathan-Huckleberry/crypto-HCTR2-support/20220427-084044
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
:::::: branch date: 9 hours ago
:::::: commit date: 9 hours ago
config: i386-randconfig-s002-20220425 (https://download.01.org/0day-ci/archive/20220427/202204271747.9NI6Iyxe-lkp(a)intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/intel-lab-lkp/linux/commit/00cd244c8a1bd9623a271407bf10b99c01884ef5
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Nathan-Huckleberry/crypto-HCTR2-support/20220427-084044
git checkout 00cd244c8a1bd9623a271407bf10b99c01884ef5
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/crypto/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> arch/x86/crypto/aesni-intel_glue.c:1287:1: sparse: sparse: unused label 'unregister_aeads'
vim +/unregister_aeads +1287 arch/x86/crypto/aesni-intel_glue.c
00cd244c8a1bd9 Nathan Huckleberry 2022-04-27 1284
85671860caaca2 Herbert Xu 2016-11-22 1285 return 0;
85671860caaca2 Herbert Xu 2016-11-22 1286
00cd244c8a1bd9 Nathan Huckleberry 2022-04-27 @1287 unregister_aeads:
00cd244c8a1bd9 Nathan Huckleberry 2022-04-27 1288 simd_unregister_aeads(aesni_aeads, ARRAY_SIZE(aesni_aeads),
00cd244c8a1bd9 Nathan Huckleberry 2022-04-27 1289 aesni_simd_aeads);
85671860caaca2 Herbert Xu 2016-11-22 1290 unregister_skciphers:
8b56d3488d8755 Eric Biggers 2019-03-10 1291 simd_unregister_skciphers(aesni_skciphers, ARRAY_SIZE(aesni_skciphers),
8b56d3488d8755 Eric Biggers 2019-03-10 1292 aesni_simd_skciphers);
07269559ac0bf7 Eric Biggers 2019-06-02 1293 unregister_cipher:
07269559ac0bf7 Eric Biggers 2019-06-02 1294 crypto_unregister_alg(&aesni_cipher_alg);
af05b3009b6b10 Herbert Xu 2015-05-28 1295 return err;
54b6a1bd5364ac Huang Ying 2009-01-18 1296 }
54b6a1bd5364ac Huang Ying 2009-01-18 1297
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-04-27 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 9:56 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-27 9:12 [PATCH v5 4/8] crypto: x86/aesni-xctr: Add accelerated implementation of XCTR kernel test robot
2022-04-27 0:37 [PATCH v5 0/8] crypto: HCTR2 support Nathan Huckleberry
2022-04-27 0:37 ` [PATCH v5 4/8] crypto: x86/aesni-xctr: Add accelerated implementation of XCTR Nathan Huckleberry
2022-04-27 0:37 ` Nathan Huckleberry
2022-04-27 4:26 ` kernel test robot
2022-05-01 21:31 ` Eric Biggers
2022-05-01 21:31 ` Eric Biggers
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=202204271747.9NI6Iyxe-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.