From: Longfang Liu <liulongfang@huawei.com>
To: <herbert@gondor.apana.org.au>, <wangzhou1@hisilicon.com>,
<xuzaibo@huawei.com>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v4 1/3] crypto: hisilicon/sec - fixes a printing error
Date: Sat, 13 Mar 2021 15:28:23 +0800 [thread overview]
Message-ID: <1615620505-50018-2-git-send-email-liulongfang@huawei.com> (raw)
In-Reply-To: <1615620505-50018-1-git-send-email-liulongfang@huawei.com>
When the log is output here, the device has not
been initialized yet.
Signed-off-by: Longfang Liu <liulongfang@huawei.com>
---
drivers/crypto/hisilicon/sec2/sec_crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/hisilicon/sec2/sec_crypto.c b/drivers/crypto/hisilicon/sec2/sec_crypto.c
index f835514..2176e4d 100644
--- a/drivers/crypto/hisilicon/sec2/sec_crypto.c
+++ b/drivers/crypto/hisilicon/sec2/sec_crypto.c
@@ -546,7 +546,7 @@ static int sec_skcipher_init(struct crypto_skcipher *tfm)
crypto_skcipher_set_reqsize(tfm, sizeof(struct sec_req));
ctx->c_ctx.ivsize = crypto_skcipher_ivsize(tfm);
if (ctx->c_ctx.ivsize > SEC_IV_SIZE) {
- dev_err(SEC_CTX_DEV(ctx), "get error skcipher iv size!\n");
+ pr_err("get error skcipher iv size!\n");
return -EINVAL;
}
--
2.8.1
next prev parent reply other threads:[~2021-03-13 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 7:28 [PATCH v4 0/3] crypto:hisilicon/sec - fixes some coding style Longfang Liu
2021-03-13 7:28 ` Longfang Liu [this message]
2021-03-13 7:28 ` [PATCH v4 2/3] crypto: hisilicon/sec " Longfang Liu
2021-03-13 7:28 ` [PATCH v4 3/3] crypto: hisilicon/sec - fixes some driver " Longfang Liu
2021-03-19 11:04 ` [PATCH v4 0/3] crypto:hisilicon/sec - fixes some " Herbert Xu
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=1615620505-50018-2-git-send-email-liulongfang@huawei.com \
--to=liulongfang@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=xuzaibo@huawei.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).