From: Radu Nicolau <radu.nicolau@intel.com>
To: Pratik Senapati <psenapati@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Akhil Goyal <gakhil@marvell.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"kai.ji@intel.com" <kai.ji@intel.com>
Subject: Re: [EXTERNAL] Re: [PATCH v4 1/4] app/crypto-perf: support mldsa Sign-Iteration
Date: Thu, 1 Oct 2026 17:10:56 +0100 [thread overview]
Message-ID: <9df33b27-970c-4f9a-a452-36ba6c6eb92b@intel.com> (raw)
In-Reply-To: <LV8PR18MB6078F14394D1B1812C574D15BD8A2@LV8PR18MB6078.namprd18.prod.outlook.com>
On 01-Oct-26 3:58 PM, Pratik Senapati wrote:
>> Series-tested-by: Radu Nicolau <radu.nicolau@intel.com>
> Hi,
>
> I checked your patch-set, and my patch-set DOES NOT have the following patches:
>
> - ML-DSA sign: non-deterministic, sha3_256, and ext-mu variants for 65 and 87 (6 cases)
> - ML-KEM encap: non-deterministic (random message) variants for 768 and 1024 (2 cases)
>
> My patchset doesn't have the above patches since it was out of scope for our requirements.
>
> To conclude:
>
> We can do the following:
> - I can include your test-cases and add your sign-off.
> - We can accept your patch-set and reject mine.
>
> Please let me know what you'd like to do.
>
> Thanks,
> Pratik
Hi,
The best approach, which includes most of our work, will be:
1. retain my patch for the test app, which covers more test cases.
2. retain your patchset for the crypto-perf app, which has all the
variants that mine has, and in addition the sign iterations argument.
Regards,
Radu
next prev parent reply other threads:[~2026-10-01 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:38 [PATCH v2 1/4] app/crypto-perf: support mldsa Sign-Iteration Pratik Senapati
2026-09-28 16:38 ` [PATCH v2 2/4] app/crypto-perf: add ML-KEM support Pratik Senapati
2026-09-28 16:38 ` [PATCH v2 3/4] app/crypto-perf: add ML-DSA support Pratik Senapati
2026-09-28 16:38 ` [PATCH v2 4/4] app/crypto-perf: add ML-DSA sign support Pratik Senapati
2026-09-29 10:58 ` [PATCH v3 1/4] app/crypto-perf: support mldsa Sign-Iteration Pratik Senapati
2026-09-29 10:58 ` [PATCH v3 2/4] app/crypto-perf: add ML-KEM support Pratik Senapati
2026-09-29 10:58 ` [PATCH v3 3/4] app/crypto-perf: add ML-DSA support Pratik Senapati
2026-09-29 10:58 ` [PATCH v3 4/4] app/crypto-perf: add ML-DSA sign support Pratik Senapati
2026-09-29 12:20 ` [PATCH v4 1/4] app/crypto-perf: support mldsa Sign-Iteration Pratik Senapati
2026-09-29 12:20 ` [PATCH v4 2/4] app/crypto-perf: add ML-KEM support Pratik Senapati
2026-09-29 12:20 ` [PATCH v4 3/4] app/crypto-perf: add ML-DSA support Pratik Senapati
2026-09-29 12:20 ` [PATCH v4 4/4] app/crypto-perf: add ML-DSA sign support Pratik Senapati
2026-09-30 11:58 ` [PATCH v4 1/4] app/crypto-perf: support mldsa Sign-Iteration Radu Nicolau
2026-10-01 14:58 ` [EXTERNAL] " Pratik Senapati
2026-10-01 16:10 ` Radu Nicolau [this message]
2026-10-05 18:02 ` Akhil Goyal
2026-10-06 9:05 ` [PATCH " Pratik Senapati
2026-10-06 9:05 ` [PATCH 2/4] app/crypto-perf: add ML-KEM support Pratik Senapati
2026-10-06 9:05 ` [PATCH 3/4] app/crypto-perf: add ML-DSA support Pratik Senapati
2026-10-06 9:05 ` [PATCH 4/4] app/crypto-perf: add ML-DSA sign support Pratik Senapati
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=9df33b27-970c-4f9a-a452-36ba6c6eb92b@intel.com \
--to=radu.nicolau@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@marvell.com \
--cc=kai.ji@intel.com \
--cc=psenapati@marvell.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