From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>, <dev@dpdk.org>
Subject: RE: [PATCH v2 0/6] crypto: use timing-safe digest comparison
Date: Tue, 30 Jun 2026 19:22:45 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F6594B@smartserver.smartshare.dk> (raw)
In-Reply-To: <20260629190027.2071745-1-stephen@networkplumber.org>
Series-acked-by: Morten Brørup <mb@smartsharesystems.com>
prev parent reply other threads:[~2026-06-30 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 15:56 [PATCH 0/5] crypto: use timing-safe digest comparison Stephen Hemminger
2026-06-25 15:56 ` [PATCH 1/5] eal: take experimental flag off of rte_memeq_timingsafe Stephen Hemminger
2026-06-25 15:56 ` [PATCH 2/5] crypto/uadk: use timing-safe digest comparison Stephen Hemminger
2026-06-25 15:56 ` [PATCH 3/5] crypto/ccp: " Stephen Hemminger
2026-06-25 15:56 ` [PATCH 4/5] crypto/armv8: " Stephen Hemminger
2026-06-26 17:11 ` Jack Bond-Preston
2026-06-25 15:56 ` [PATCH 5/5] crypto/cnxk: " Stephen Hemminger
2026-06-29 6:42 ` [EXTERNAL] " Tejasree Kondoj
2026-06-29 7:38 ` [EXTERNAL] [PATCH 0/5] crypto: " Akhil Goyal
2026-06-29 18:59 ` [PATCH v2 0/6] " Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 1/6] eal: take experimental flag off of rte_memeq_timingsafe Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 2/6] crypto/uadk: use timing-safe digest comparison Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 3/6] crypto/ccp: " Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 4/6] crypto/armv8: " Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 5/6] crypto/cnxk: " Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 6/6] crypto/octeontx: use timing-safe RSA signature verification Stephen Hemminger
2026-06-30 9:50 ` [EXTERNAL] " Tejasree Kondoj
2026-06-30 17:22 ` Morten Brørup [this message]
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=98CBD80474FA8B44BF855DF32C47DC35F6594B@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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.