* [linux-next:master 7715/9581] drivers/crypto/cavium/cpt/cptvf_algs.c:225:5: sparse: symbol 'cvm_encrypt' was not declared. Should it be static?
@ 2017-06-23 13:10 kbuild test robot
2017-06-23 13:10 ` [RFC PATCH linux-next] crypto: cvm_encrypt() can be static kbuild test robot
0 siblings, 1 reply; 2+ messages in thread
From: kbuild test robot @ 2017-06-23 13:10 UTC (permalink / raw)
To: George Cherian; +Cc: kbuild-all, Herbert Xu, linux-crypto, linux-kernel
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: a73468728fd8f34ccbd7c60f0808024ae491f4d6
commit: e2eb769ed0bdc06cb523f475db411ce3a5f1c465 [7715/9581] crypto: cavium - Remove the individual encrypt/decrypt function for each algorithm
reproduce:
# apt-get install sparse
git checkout e2eb769ed0bdc06cb523f475db411ce3a5f1c465
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
drivers/crypto/cavium/cpt/cptvf_algs.c:135:21: sparse: incorrect type in assignment (different base types)
drivers/crypto/cavium/cpt/cptvf_algs.c:135:21: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident>
drivers/crypto/cavium/cpt/cptvf_algs.c:135:21: got restricted __be64 [usertype] <noident>
drivers/crypto/cavium/cpt/cptvf_algs.c:137:25: sparse: incorrect type in assignment (different base types)
drivers/crypto/cavium/cpt/cptvf_algs.c:137:25: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident>
drivers/crypto/cavium/cpt/cptvf_algs.c:137:25: got restricted __be64 [usertype] <noident>
>> drivers/crypto/cavium/cpt/cptvf_algs.c:225:5: sparse: symbol 'cvm_encrypt' was not declared. Should it be static?
drivers/crypto/cavium/cpt/cptvf_algs.c:135:21: sparse: incorrect type in assignment (different base types)
drivers/crypto/cavium/cpt/cptvf_algs.c:135:21: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident>
drivers/crypto/cavium/cpt/cptvf_algs.c:135:21: got restricted __be64 [usertype] <noident>
drivers/crypto/cavium/cpt/cptvf_algs.c:137:25: sparse: incorrect type in assignment (different base types)
drivers/crypto/cavium/cpt/cptvf_algs.c:137:25: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident>
drivers/crypto/cavium/cpt/cptvf_algs.c:137:25: got restricted __be64 [usertype] <noident>
>> drivers/crypto/cavium/cpt/cptvf_algs.c:230:5: sparse: symbol 'cvm_decrypt' was not declared. Should it be static?
drivers/crypto/cavium/cpt/cptvf_algs.c:235:5: sparse: symbol 'cvm_xts_setkey' was not declared. Should it be static?
drivers/crypto/cavium/cpt/cptvf_algs.c:321:5: sparse: symbol 'cvm_enc_dec_init' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
^ permalink raw reply [flat|nested] 2+ messages in thread
* [RFC PATCH linux-next] crypto: cvm_encrypt() can be static
2017-06-23 13:10 [linux-next:master 7715/9581] drivers/crypto/cavium/cpt/cptvf_algs.c:225:5: sparse: symbol 'cvm_encrypt' was not declared. Should it be static? kbuild test robot
@ 2017-06-23 13:10 ` kbuild test robot
0 siblings, 0 replies; 2+ messages in thread
From: kbuild test robot @ 2017-06-23 13:10 UTC (permalink / raw)
To: George Cherian; +Cc: kbuild-all, Herbert Xu, linux-crypto, linux-kernel
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
cptvf_algs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/cavium/cpt/cptvf_algs.c b/drivers/crypto/cavium/cpt/cptvf_algs.c
index 443c362..4303674 100644
--- a/drivers/crypto/cavium/cpt/cptvf_algs.c
+++ b/drivers/crypto/cavium/cpt/cptvf_algs.c
@@ -222,12 +222,12 @@ static inline int cvm_enc_dec(struct ablkcipher_request *req, u32 enc)
return -EINPROGRESS;
}
-int cvm_encrypt(struct ablkcipher_request *req)
+static int cvm_encrypt(struct ablkcipher_request *req)
{
return cvm_enc_dec(req, true);
}
-int cvm_decrypt(struct ablkcipher_request *req)
+static int cvm_decrypt(struct ablkcipher_request *req)
{
return cvm_enc_dec(req, false);
}
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-06-23 13:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-23 13:10 [linux-next:master 7715/9581] drivers/crypto/cavium/cpt/cptvf_algs.c:225:5: sparse: symbol 'cvm_encrypt' was not declared. Should it be static? kbuild test robot
2017-06-23 13:10 ` [RFC PATCH linux-next] crypto: cvm_encrypt() can be static kbuild test robot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).