From: kbuild test robot <lkp@intel.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: kbuild-all@01.org, linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: [RFC PATCH cryptodev] crypto: cc_sec_disable can be static
Date: Fri, 26 Apr 2019 09:03:09 +0800 [thread overview]
Message-ID: <20190426010309.GA57833@ivb42> (raw)
In-Reply-To: <201904260948.KwQ0CBJd%lkp@intel.com>
Fixes: f98f6e2134bd ("crypto: ccree - add support for sec disabled mode")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
cc_driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/ccree/cc_driver.c b/drivers/crypto/ccree/cc_driver.c
index 255d236..13b54a2 100644
--- a/drivers/crypto/ccree/cc_driver.c
+++ b/drivers/crypto/ccree/cc_driver.c
@@ -35,7 +35,7 @@ bool cc_dump_bytes;
module_param_named(dump_bytes, cc_dump_bytes, bool, 0600);
MODULE_PARM_DESC(cc_dump_bytes, "Dump buffers to kernel log as debugging aid");
-bool cc_sec_disable;
+static bool cc_sec_disable;
module_param_named(sec_disable, cc_sec_disable, bool, 0600);
MODULE_PARM_DESC(cc_sec_disable, "Disable security functions");
next prev parent reply other threads:[~2019-04-26 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 1:03 [cryptodev:master 130/163] drivers/crypto/ccree/cc_driver.c:38:6: sparse: sparse: symbol 'cc_sec_disable' was not declared. Should it be static? kbuild test robot
2019-04-26 1:03 ` kbuild test robot [this message]
2019-04-28 7:10 ` [RFC PATCH cryptodev] crypto: cc_sec_disable can be static Gilad Ben-Yossef
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=20190426010309.GA57833@ivb42 \
--to=lkp@intel.com \
--cc=gilad@benyossef.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@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;
as well as URLs for NNTP newsgroup(s).