[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202211031730.l7JO8DqW-lkp@intel.com>
Date: Thu, 3 Nov 2022 17:26:11 +0800
From: kernel test robot <lkp@...el.com>
To: Robert Elliott <elliott@....com>, herbert@...dor.apana.org.au,
davem@...emloft.net, tim.c.chen@...ux.intel.com,
ap420073@...il.com, ardb@...nel.org, Jason@...c4.com,
David.Laight@...lab.com, ebiggers@...nel.org,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: oe-kbuild-all@...ts.linux.dev, Robert Elliott <elliott@....com>
Subject: Re: [PATCH v3 11/17] crypto: x86/sha - register all variations
Hi Robert,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on v6.1-rc2]
[also build test WARNING on next-20221103]
[cannot apply to herbert-cryptodev-2.6/master herbert-crypto-2.6/master crng-random/master linus/master v6.1-rc3]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Robert-Elliott/crypto-tcrypt-test-crc32/20221103-132823
patch link: https://lore.kernel.org/r/20221103042740.6556-12-elliott%40hpe.com
patch subject: [PATCH v3 11/17] crypto: x86/sha - register all variations
config: x86_64-allyesconfig
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/70c392540055e5e494696b9f4fb6db52f2b6574c
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Robert-Elliott/crypto-tcrypt-test-crc32/20221103-132823
git checkout 70c392540055e5e494696b9f4fb6db52f2b6574c
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/crypto/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@...el.com>
All warnings (new ones prefixed by >>):
arch/x86/crypto/sha1_ssse3_glue.c: In function 'sha1_ssse3_mod_init':
>> arch/x86/crypto/sha1_ssse3_glue.c:302:21: warning: variable 'driver_name' set but not used [-Wunused-but-set-variable]
302 | const char *driver_name = NULL;
| ^~~~~~~~~~~
--
arch/x86/crypto/sha256_ssse3_glue.c: In function 'sha256_ssse3_mod_init':
>> arch/x86/crypto/sha256_ssse3_glue.c:365:21: warning: variable 'driver_name2' set but not used [-Wunused-but-set-variable]
365 | const char *driver_name2 = NULL;
| ^~~~~~~~~~~~
>> arch/x86/crypto/sha256_ssse3_glue.c:364:21: warning: variable 'driver_name' set but not used [-Wunused-but-set-variable]
364 | const char *driver_name = NULL;
| ^~~~~~~~~~~
--
arch/x86/crypto/sha512_ssse3_glue.c: In function 'sha512_ssse3_mod_init':
>> arch/x86/crypto/sha512_ssse3_glue.c:304:21: warning: variable 'driver_name2' set but not used [-Wunused-but-set-variable]
304 | const char *driver_name2 = NULL;
| ^~~~~~~~~~~~
>> arch/x86/crypto/sha512_ssse3_glue.c:303:21: warning: variable 'driver_name' set but not used [-Wunused-but-set-variable]
303 | const char *driver_name = NULL;
| ^~~~~~~~~~~
vim +/driver_name +302 arch/x86/crypto/sha1_ssse3_glue.c
298
299 static int __init sha1_ssse3_mod_init(void)
300 {
301 const char *feature_name;
> 302 const char *driver_name = NULL;
303 int ret;
304
--
0-DAY CI Kernel Test Service
https://01.org/lkp
View attachment "config" of type "text/plain" (291877 bytes)
Powered by blists - more mailing lists