From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH] arm: crypto: initialize digests earlier
Date: Tue, 6 Feb 2018 08:34:54 +0100 [thread overview]
Message-ID: <20180206073454.18911-1-s.hauer@pengutronix.de> (raw)
We moved the digest init functions to coredevice_initcall level. Do
the same with the ARM specific digests aswell so that they are available
at the same time.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/arm/crypto/sha1_glue.c | 2 +-
arch/arm/crypto/sha256_glue.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/crypto/sha1_glue.c b/arch/arm/crypto/sha1_glue.c
index 57cd9d1014..cc032f6af2 100644
--- a/arch/arm/crypto/sha1_glue.c
+++ b/arch/arm/crypto/sha1_glue.c
@@ -135,4 +135,4 @@ static int sha1_mod_init(void)
{
return digest_algo_register(&m);
}
-device_initcall(sha1_mod_init);
+coredevice_initcall(sha1_mod_init);
diff --git a/arch/arm/crypto/sha256_glue.c b/arch/arm/crypto/sha256_glue.c
index e649609a8e..d8a72a2cb9 100644
--- a/arch/arm/crypto/sha256_glue.c
+++ b/arch/arm/crypto/sha256_glue.c
@@ -189,7 +189,7 @@ static int sha224_digest_register(void)
{
return digest_algo_register(&sha224);
}
-device_initcall(sha224_digest_register);
+coredevice_initcall(sha224_digest_register);
static struct digest_algo sha256 = {
.base = {
@@ -212,4 +212,4 @@ static int sha256_digest_register(void)
{
return digest_algo_register(&sha256);
}
-device_initcall(sha256_digest_register);
+coredevice_initcall(sha256_digest_register);
--
2.15.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2018-02-06 7:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180206073454.18911-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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