From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org
Cc: Daniel Kiper <dkiper@net-space.pl>,
Leo Sandoval <lsandova@redhat.com>,
Glenn Washburn <development@efficientek.com>
Subject: [PATCH 0/2] Expect success for argon2 cryptomount test
Date: Mon, 17 Nov 2025 00:40:24 -0600 [thread overview]
Message-ID: <cover.1763360459.git.development@efficientek.com> (raw)
Patch #1 fixes a fialing test caused by argon2 integration (which is
expected because it was written to verify that GRUB could not open
LUKS2 volumes using an Argon2 keyslot).
The second patch, fixes potential issues with having spaces in the
builddir path and puts the builddir autoconf macro into a variable
so it only gets expanded once.
Glenn
Glenn Washburn (2):
tests/grub_cmd_cryptomount: Expect test success, now that GRUB
supports Argon2
tests/grub_cmd_cryptomount: Use builddir shell variable and quote
tests/grub_cmd_cryptomount.in | 50 +++++++++++++++++------------------
1 file changed, 25 insertions(+), 25 deletions(-)
--
2.34.1
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2025-11-17 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 6:40 Glenn Washburn [this message]
2025-11-17 6:40 ` [PATCH 1/2] tests/grub_cmd_cryptomount: Expect test success, now that GRUB supports Argon2 Glenn Washburn
2025-11-18 6:35 ` Sudhakar Kuppusamy
2025-11-17 6:40 ` [PATCH 2/2] tests/grub_cmd_cryptomount: Use builddir shell variable and quote Glenn Washburn
2025-11-18 6:35 ` Sudhakar Kuppusamy
2025-11-17 17:46 ` [PATCH 0/2] Expect success for argon2 cryptomount test Daniel Kiper
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=cover.1763360459.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=lsandova@redhat.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