From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android-4.19 1/2] drivers/scsi/ufs/ufshcd-crypto.c:250:26: warning: no previous prototype for function 'ufshcd_blk_crypto_mode_num_for_alg_dusize'
Date: Tue, 19 Jan 2021 20:39:59 +0800 [thread overview]
Message-ID: <202101192049.v9vpRvJt-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2612 bytes --]
tree: https://android.googlesource.com/kernel/common android-4.19
head: 9e25a3c2aea5621981b002e8c9b45553dc44112a
commit: b01c73ea7129745ce9d94b8d3b35663b716cd95b [1/2] BACKPORT: FROMLIST: Update Inline Encryption from v5 to v6 of patch series
config: x86_64-randconfig-a013-20210119 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 22b68440e1647e16b5ee24b924986207173c02d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android-4.19
git checkout b01c73ea7129745ce9d94b8d3b35663b716cd95b
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/scsi/ufs/ufshcd-crypto.c:250:26: warning: no previous prototype for function 'ufshcd_blk_crypto_mode_num_for_alg_dusize' [-Wmissing-prototypes]
enum blk_crypto_mode_num ufshcd_blk_crypto_mode_num_for_alg_dusize(
^
drivers/scsi/ufs/ufshcd-crypto.c:250:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
enum blk_crypto_mode_num ufshcd_blk_crypto_mode_num_for_alg_dusize(
^
static
1 warning generated.
drivers/scsi/ufs/ufshcd-crypto.c:272: warning: Function parameter or member 'ksm_ops' not described in 'ufshcd_hba_init_crypto_spec'
vim +/ufshcd_blk_crypto_mode_num_for_alg_dusize +250 drivers/scsi/ufs/ufshcd-crypto.c
249
> 250 enum blk_crypto_mode_num ufshcd_blk_crypto_mode_num_for_alg_dusize(
251 enum ufs_crypto_alg ufs_crypto_alg,
252 enum ufs_crypto_key_size key_size)
253 {
254 /*
255 * This is currently the only mode that UFS and blk-crypto both support.
256 */
257 if (ufs_crypto_alg == UFS_CRYPTO_ALG_AES_XTS &&
258 key_size == UFS_CRYPTO_KEY_SIZE_256)
259 return BLK_ENCRYPTION_MODE_AES_256_XTS;
260
261 return BLK_ENCRYPTION_MODE_INVALID;
262 }
263
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 39068 bytes --]
reply other threads:[~2021-01-19 12:39 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=202101192049.v9vpRvJt-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@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.