From: Akhil Goyal <gakhil@marvell.com>
To: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Koteswara Rao Kottidi <skoteshwar@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] [PATCH 1/3] common/cnxk: add const values to ec groups
Date: Tue, 27 Jul 2021 17:34:32 +0000 [thread overview]
Message-ID: <PH0PR18MB4491132C8AE58D2994A3BFF1D8E99@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210726044853.2232433-1-kirankumark@marvell.com>
>
> New ucode expects const values A and B for asymmetric ECDSA
> messages. Adding roc support for this.
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> ---
Series Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2021-07-27 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 4:48 [dpdk-dev] " kirankumark
2021-07-26 4:48 ` [dpdk-dev] [PATCH 2/3] crypto/cnxk: update asym ECDSA messages in sync with ucode kirankumark
2021-07-26 4:48 ` [dpdk-dev] [PATCH 3/3] common/cpt: " kirankumark
2021-07-27 17:34 ` 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=PH0PR18MB4491132C8AE58D2994A3BFF1D8E99@PH0PR18MB4491.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@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;
as well as URLs for NNTP newsgroup(s).