From: kbuild test robot <fengguang.wu@intel.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: kbuild-all@01.org, Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Ofir Drang <ofir.drang@arm.com>, Hadar Gat <hadar.gat@arm.com>,
stable@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH] crypto: ccree: cc_update_ctr() can be static
Date: Thu, 28 Jun 2018 19:42:37 +0800 [thread overview]
Message-ID: <20180628114237.GA119685@athens> (raw)
In-Reply-To: <1530171175-31960-4-git-send-email-gilad@benyossef.com>
Fixes: 27646566a1a0 ("crypto: ccree: fix iv handling")
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
cc_cipher.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/ccree/cc_cipher.c b/drivers/crypto/ccree/cc_cipher.c
index 3af44a5..958ced3 100644
--- a/drivers/crypto/ccree/cc_cipher.c
+++ b/drivers/crypto/ccree/cc_cipher.c
@@ -596,7 +596,7 @@ static void cc_setup_cipher_data(struct crypto_tfm *tfm,
/*
* Update a CTR-AES 128 bit counter
*/
-void cc_update_ctr(u8 *ctr, unsigned int increment)
+static void cc_update_ctr(u8 *ctr, unsigned int increment)
{
if (IS_ENABLED(CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS) ||
IS_ALIGNED((unsigned long)ctr, 8)) {
next prev parent reply other threads:[~2018-06-28 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 7:32 [PATCH 0/4] crypto: fixes and cleanups Gilad Ben-Yossef
2018-06-28 7:32 ` [PATCH 1/4] crypto: ccree: fix finup Gilad Ben-Yossef
2018-06-28 7:32 ` [PATCH 2/4] crypto: testmgr: add hash finup tests Gilad Ben-Yossef
2018-06-28 7:32 ` [PATCH 3/4] crypto: ccree: fix iv handling Gilad Ben-Yossef
2018-06-28 11:42 ` kbuild test robot
2018-06-28 11:42 ` kbuild test robot [this message]
2018-06-28 7:32 ` [PATCH 4/4] crypto: ccree: remove dead legacy code 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=20180628114237.GA119685@athens \
--to=fengguang.wu@intel.com \
--cc=davem@davemloft.net \
--cc=gilad@benyossef.com \
--cc=hadar.gat@arm.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ofir.drang@arm.com \
--cc=stable@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 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.