From: Vladimir Serbinenko <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: [PATCH v13 00/13] Upgrade to libgcrypt 1.11
Date: Sat, 24 May 2025 20:22:52 +0000 [thread overview]
Message-ID: <20250524202424.840406-1-phcoder@gmail.com> (raw)
Upgrade to libgcrypt 1.11
Changes from v12:
* Import blake_vl_hash
* Remove changes to b64dec and use a special header instead
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2025-05-24 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 20:22 Vladimir Serbinenko [this message]
2025-05-24 20:22 ` [PATCH v13 01/13] Import libgcrypt 1.11 Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 02/13] Import b64dec from gpg-error Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 03/13] b64dec: Add harness for compilation in GRUB environment Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 04/13] Adjust import script, definitions and API users for libgcrypt 1.11 Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 05/13] Add DSA and RSA SEXP tests Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 06/13] keccak: Disable acceleration with SSE asm Vladimir Serbinenko
2025-05-24 20:22 ` [PATCH v13 07/13] libgcrypt: Fix coverity warnings Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 08/13] Remove now unneeded gcrypt compilation flag Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 09/13] gcry: Ignore sign-compare warnings Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 10/13] libgcrypt: Import blake family of hashes Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 11/13] import_gcry: Make compatible with python 3.4 Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 12/13] import_gcry: Fix pylint warnings Vladimir Serbinenko
2025-05-24 20:23 ` [PATCH v13 13/13] libgcrypt: Don't use 64-bit division on platforms where it's slow Vladimir Serbinenko
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=20250524202424.840406-1-phcoder@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.