From: Marek Vasut <marex@denx.de>
To: linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, Marek Vasut <marex@denx.de>
Subject: [PATCH 6/7] crypto: padlock: Don't use tfm->__crt_alg->cra_name directly
Date: Wed, 14 May 2014 11:41:02 +0200 [thread overview]
Message-ID: <1400060463-11644-6-git-send-email-marex@denx.de> (raw)
In-Reply-To: <1400060463-11644-1-git-send-email-marex@denx.de>
Signed-off-by: Marek Vasut <marex@denx.de>
---
drivers/crypto/padlock-sha.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
NOTE: I didn't compile-test those, but the change should not break anything.
If possible, please test on relevant hardware.
diff --git a/drivers/crypto/padlock-sha.c b/drivers/crypto/padlock-sha.c
index 9266c0e..bace885 100644
--- a/drivers/crypto/padlock-sha.c
+++ b/drivers/crypto/padlock-sha.c
@@ -211,7 +211,7 @@ static int padlock_sha256_final(struct shash_desc *desc, u8 *out)
static int padlock_cra_init(struct crypto_tfm *tfm)
{
struct crypto_shash *hash = __crypto_shash_cast(tfm);
- const char *fallback_driver_name = tfm->__crt_alg->cra_name;
+ const char *fallback_driver_name = crypto_tfm_alg_name(tfm);
struct padlock_sha_ctx *ctx = crypto_tfm_ctx(tfm);
struct crypto_shash *fallback_tfm;
int err = -ENOMEM;
--
2.0.0.rc0
next prev parent reply other threads:[~2014-05-14 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 9:40 [PATCH 1/7] crypto: geode: Don't use tfm->__crt_alg->cra_name directly Marek Vasut
2014-05-14 9:40 ` [PATCH 2/7] crypto: ccp: " Marek Vasut
2014-05-14 9:40 ` [PATCH 3/7] crypto: cesa: " Marek Vasut
2014-05-14 9:41 ` [PATCH 4/7] crypto: dcp: " Marek Vasut
2014-05-14 9:41 ` [PATCH 5/7] crypto: n2: " Marek Vasut
2014-05-14 9:41 ` Marek Vasut [this message]
2014-05-14 9:41 ` [PATCH 7/7] crypto: sahara: " Marek Vasut
2014-05-22 13:09 ` [PATCH 1/7] crypto: geode: " 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=1400060463-11644-6-git-send-email-marex@denx.de \
--to=marex@denx.de \
--cc=herbert@gondor.apana.org.au \
--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).