From: Akhil Goyal <gakhil@marvell.com>
To: Sucharitha Sarananaga <ssarananaga@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>,
Sucharitha Sarananaga <ssarananaga@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] app/test: update EdDSA test vector description
Date: Tue, 17 Jun 2025 21:24:47 +0000 [thread overview]
Message-ID: <CO6PR18MB448454571BC0FA7D56E8BBFFD873A@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250616063350.2507803-1-ssarananaga@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 44 bytes --]
Recheck-request: iol-compile-amd64-testing
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 14791 bytes --]
prev parent reply other threads:[~2025-06-17 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 6:33 Sucharitha Sarananaga
2025-06-17 21:24 ` Akhil Goyal [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=CO6PR18MB448454571BC0FA7D56E8BBFFD873A@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=ssarananaga@marvell.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).