From: Heiko Schocher <hs@nabladev.com>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Heiko Schocher <hs@nabladev.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Jerome Forissier <jerome.forissier@linaro.org>,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
Tom Rini <trini@konsulko.com>
Subject: [PATCH v1 5/5] test: cmd: fix a typo in md5 test
Date: Sat, 1 Nov 2025 07:49:07 +0100 [thread overview]
Message-ID: <20251101064907.5037-6-hs@nabladev.com> (raw)
In-Reply-To: <20251101064907.5037-1-hs@nabladev.com>
In dm_test_cmd_hash_md5 accidentially sha256 hash
ist used. Use the correct md5 hash instead.
Signed-off-by: Heiko Schocher <hs@nabladev.com>
---
test/cmd/hash.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/cmd/hash.c b/test/cmd/hash.c
index 3f7f64d27d3..3a3869831ce 100644
--- a/test/cmd/hash.c
+++ b/test/cmd/hash.c
@@ -38,7 +38,7 @@ static int dm_test_cmd_hash_md5(struct unit_test_state *uts)
"d41d8cd98f00b204e9800998ecf8427e"));
if (!CONFIG_IS_ENABLED(HASH_VERIFY)) {
- ut_assert(run_command("hash -v sha256 $loadaddr 0 foo", 0));
+ ut_assert(run_command("hash -v md5 $loadaddr 0 foo", 0));
ut_assertok(ut_check_console_line(
uts, "hash - compute hash message digest"));
--
2.20.1
next prev parent reply other threads:[~2025-11-01 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 6:49 [PATCH v1 0/5] Add support for SM3 secure hash Heiko Schocher
2025-11-01 6:49 ` [PATCH v1 1/5] lib: Import rol32 function from Linux Heiko Schocher
2025-11-01 6:49 ` [PATCH v1 2/5] lib: implement SM3 secure hash Heiko Schocher
2025-11-01 17:11 ` Raymond Mao
2025-11-03 8:56 ` Heiko Schocher
2025-11-04 2:30 ` Raymond Mao
2025-11-01 6:49 ` [PATCH v1 3/5] test: cmd: add unit test for sm3 hash Heiko Schocher
2025-11-01 6:49 ` [PATCH v1 4/5] tpm2: add sm3 256 hash support Heiko Schocher
2025-11-10 11:51 ` Ilias Apalodimas
2025-11-10 13:06 ` Heiko Schocher
2025-11-01 6:49 ` Heiko Schocher [this message]
2025-11-01 7:45 ` [PATCH v1 5/5] test: cmd: fix a typo in md5 test Heinrich Schuchardt
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=20251101064907.5037-6-hs@nabladev.com \
--to=hs@nabladev.com \
--cc=jerome.forissier@linaro.org \
--cc=mkorpershoek@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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