From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Chen Gang <gang.chen@sunrus.com.cn>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
schwidefsky@de.ibm.com, linux390@de.ibm.com,
linux-crypto@vger.kernel.org, linux-s390@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] s390: crypto: aes_s390: Remove 'const' to avoid compiler warnings
Date: Wed, 7 Jan 2015 09:24:14 +0100 [thread overview]
Message-ID: <20150107082414.GA4365@osiris> (raw)
In-Reply-To: <54A56002.3000301@sunrus.com.cn>
On Thu, Jan 01, 2015 at 10:56:02PM +0800, Chen Gang wrote:
> In aes_encrypt() and aes_decrypt(), need let 'sctx->key' be modified,
> so remove 'const' for it. The related warnings:
...
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> ---
> arch/s390/crypto/aes_s390.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/s390/crypto/aes_s390.c b/arch/s390/crypto/aes_s390.c
> index 1f272b2..5566ce8 100644
> --- a/arch/s390/crypto/aes_s390.c
> +++ b/arch/s390/crypto/aes_s390.c
> @@ -134,7 +134,7 @@ static int aes_set_key(struct crypto_tfm *tfm, const u8 *in_key,
>
> static void aes_encrypt(struct crypto_tfm *tfm, u8 *out, const u8 *in)
> {
> - const struct s390_aes_ctx *sctx = crypto_tfm_ctx(tfm);
> + struct s390_aes_ctx *sctx = crypto_tfm_ctx(tfm);
>
> if (unlikely(need_fallback(sctx->key_len))) {
> crypto_cipher_encrypt_one(sctx->fallback.cip, out, in);
> @@ -159,7 +159,7 @@ static void aes_encrypt(struct crypto_tfm *tfm, u8 *out, const u8 *in)
>
> static void aes_decrypt(struct crypto_tfm *tfm, u8 *out, const u8 *in)
> {
> - const struct s390_aes_ctx *sctx = crypto_tfm_ctx(tfm);
> + struct s390_aes_ctx *sctx = crypto_tfm_ctx(tfm);
>
> if (unlikely(need_fallback(sctx->key_len))) {
> crypto_cipher_decrypt_one(sctx->fallback.cip, out, in);
Applied, thanks.
parent reply other threads:[~2015-01-07 8:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <54A56002.3000301@sunrus.com.cn>]
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=20150107082414.GA4365@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=davem@davemloft.net \
--cc=gang.chen@sunrus.com.cn \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).