From: kernel test robot <lkp@intel.com>
To: Satya Tangirala <satyat@google.com>
Cc: kbuild-all@lists.01.org, GNU/Weeb Mailing List <gwml@gnuweeb.org>,
linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: [ammarfaizi2-block:google/android/kernel/common/android-4.14-stable 3738/9999] drivers/mmc/core/crypto.c:14:6: warning: no previous declaration for 'mmc_crypto_setup_queue'
Date: Wed, 26 Jan 2022 08:44:00 +0800 [thread overview]
Message-ID: <202201260846.mr5Y6XLD-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: 86556e67a9fde013721c184f1590930b5811505f [3738/9999] ANDROID: mmc: MMC crypto API
config: x86_64-randconfig-a002-20220124 (https://download.01.org/0day-ci/archive/20220126/202201260846.mr5Y6XLD-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/86556e67a9fde013721c184f1590930b5811505f
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 86556e67a9fde013721c184f1590930b5811505f
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash LDFLAGS=-z max-page-size=0x200000 drivers/mmc/core/
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/mmc/core/crypto.c:14:6: warning: no previous declaration for 'mmc_crypto_setup_queue' [-Wmissing-declarations]
void mmc_crypto_setup_queue(struct mmc_host *host, struct request_queue *q)
^~~~~~~~~~~~~~~~~~~~~~
>> drivers/mmc/core/crypto.c:21:6: warning: no previous declaration for 'mmc_crypto_free_host' [-Wmissing-declarations]
void mmc_crypto_free_host(struct mmc_host *host)
^~~~~~~~~~~~~~~~~~~~
>> drivers/mmc/core/crypto.c:26:6: warning: no previous declaration for 'mmc_crypto_prepare_req' [-Wmissing-declarations]
void mmc_crypto_prepare_req(struct mmc_queue_req *mqrq)
^~~~~~~~~~~~~~~~~~~~~~
vim +/mmc_crypto_setup_queue +14 drivers/mmc/core/crypto.c
13
> 14 void mmc_crypto_setup_queue(struct mmc_host *host, struct request_queue *q)
15 {
16 if (host->caps2 & MMC_CAP2_CRYPTO)
17 q->ksm = host->ksm;
18 }
19 EXPORT_SYMBOL_GPL(mmc_crypto_setup_queue);
20
> 21 void mmc_crypto_free_host(struct mmc_host *host)
22 {
23 keyslot_manager_destroy(host->ksm);
24 }
25
> 26 void mmc_crypto_prepare_req(struct mmc_queue_req *mqrq)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-26 0:44 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=202201260846.mr5Y6XLD-lkp@intel.com \
--to=lkp@intel.com \
--cc=ebiggers@google.com \
--cc=gwml@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome