[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?

mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed

From: kbuild test robot <fengguang.wu@intel.com>
To: George Cherian <george.cherian@cavium.com>
Cc: kbuild-all@01.org, Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [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?
Date: Fri, 23 Jun 2017 21:10:55 +0800	[thread overview]
Message-ID: <201706232123.X4uTYxbf%fengguang.wu@intel.com> (raw)

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

next             reply	other threads:[~2017-06-23 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 13:10 kbuild test robot [this message]
2017-06-23 13:10 ` [RFC PATCH linux-next] crypto: cvm_encrypt() can be static kbuild test robot

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=201706232123.X4uTYxbf%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=george.cherian@cavium.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kbuild-all@01.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®