From: "Barbier, Renaud" <Renaud.Barbier@ametek.com>
To: Barebox List <barebox@lists.infradead.org>
Subject: sha2 digest on ppc
Date: Fri, 18 Mar 2022 09:14:01 +0000 [thread overview]
Message-ID: <MN2PR16MB313566652F19867ADB77727F91139@MN2PR16MB3135.namprd16.prod.outlook.com> (raw)
Commit 03fb5524b06 has changed the configuration selection for hash algorithm. For instance:
-config SHA256
+config HAVE_DIGEST_SHA256
Bool
This breaks on my PPC platform as the configuration selection has not been changed in crypto/sha2.c
if (!IS_ENABLED(CONFIG_SHA256))
Still working on my ARM platform because the algo is registered somewhere else (arch/arm/crypto/sha256_glue.c)
RENAUD: sha256_digest_register
RENAUD: sha256_digest_register: ALGO NOT REGISTERED
...
RENAUD: digest_algo_get_by_name: sha256 sha256
RENAUD: digest_algo_get_by_name: sha224 sha256
RENAUD: digest_algo_get_by_name: md5 sha256
FIT: /images/kernel-1/hash-1: hash OK
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2022-03-18 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 9:14 Barbier, Renaud [this message]
2022-03-22 8:07 ` Ahmad Fatoum
2022-03-22 9:00 ` [PATCH] crypto: Followup to crypto symbol renaming for algo registration Uwe Kleine-König
2022-03-28 10:03 ` Sascha Hauer
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=MN2PR16MB313566652F19867ADB77727F91139@MN2PR16MB3135.namprd16.prod.outlook.com \
--to=renaud.barbier@ametek.com \
--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