From: kernel test robot <lkp@intel.com>
To: Satya Tangirala <satyat@google.com>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: [ammarfaizi2-block:google/android/kernel/common/android-4.14-stable 2233/9999] drivers/scsi/ufs/ufshcd-crypto.c:250:26: warning: no previous declaration for 'ufshcd_blk_crypto_mode_num_for_alg_dusize'
Date: Thu, 3 Mar 2022 05:28:40 +0800 [thread overview]
Message-ID: <202203030553.577m0VYs-lkp@intel.com> (raw)
Hi Satya,
FYI, the error/warning still remains.
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-4.14-stable
head: 4ab5bac1598e3ed91a6267f6cada336467312112
commit: e12563c18d484e6379d03105b4565db7bb3a7975 [2233/9999] BACKPORT: FROMLIST: Update Inline Encryption from v5 to v6 of patch series
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220303/202203030553.577m0VYs-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/e12563c18d484e6379d03105b4565db7bb3a7975
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android-4.14-stable
git checkout e12563c18d484e6379d03105b4565db7bb3a7975
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/mmc/core/ drivers/scsi/ufs/
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 declaration for 'ufshcd_blk_crypto_mode_num_for_alg_dusize' [-Wmissing-declarations]
enum blk_crypto_mode_num ufshcd_blk_crypto_mode_num_for_alg_dusize(
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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@lists.01.org
reply other threads:[~2022-03-02 21:28 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=202203030553.577m0VYs-lkp@intel.com \
--to=lkp@intel.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satyat@google.com \
/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.