From: Thomas Monjalon <thomas@monjalon.net>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"ciara.power@intel.com" <ciara.power@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>,
"Ji, Kai" <kai.ji@intel.com>,
"jack.bond-preston@foss.arm.com" <jack.bond-preston@foss.arm.com>,
"Marchand, David" <david.marchand@redhat.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"matan@nvidia.com" <matan@nvidia.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"chenbox@nvidia.com" <chenbox@nvidia.com>,
"sunilprakashrao.uttarwar@amd.com"
<sunilprakashrao.uttarwar@amd.com>,
"andrew.boyer@amd.com" <andrew.boyer@amd.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"raveendra.padasalagi@broadcom.com"
<raveendra.padasalagi@broadcom.com>,
"vikas.gupta@broadcom.com" <vikas.gupta@broadcom.com>,
"g.singh@nxp.com" <g.singh@nxp.com>,
"jianjay.zhou@huawei.com" <jianjay.zhou@huawei.com>,
"Daly, Lee" <lee.daly@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
"zhangfei.gao@linaro.org" <zhangfei.gao@linaro.org>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: Re: [PATCH] doc: announce cryptodev change to support EDDSA
Date: Wed, 31 Jul 2024 14:57:09 +0200 [thread overview]
Message-ID: <3258508.l52yBJDM9G@thomas> (raw)
In-Reply-To: <PH0PR11MB5013496D0BEC3AA9436BA0339FAB2@PH0PR11MB5013.namprd11.prod.outlook.com>
25/07/2024 17:01, Kusztal, ArkadiuszX:
> > Announce the additions in cryptodev ABI to support EDDSA algorithm.
> >
> > Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
>
> Acked-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Acked-by: Anoob Joseph <anoobj@marvell.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied, thanks.
It means we are not able to add an algo without breaking ABI.
Is it something we can improve?
next prev parent reply other threads:[~2024-07-31 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 14:53 Gowrishankar Muthukrishnan
2024-07-24 5:07 ` Anoob Joseph
2024-07-24 6:46 ` [EXTERNAL] " Akhil Goyal
2024-07-25 15:01 ` Kusztal, ArkadiuszX
2024-07-31 12:57 ` Thomas Monjalon [this message]
2024-08-07 17:21 ` [EXTERNAL] " Gowrishankar Muthukrishnan
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=3258508.l52yBJDM9G@thomas \
--to=thomas@monjalon.net \
--cc=abhinandan.gujjar@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.boyer@amd.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=fiona.trahe@intel.com \
--cc=g.singh@nxp.com \
--cc=gmuthukrishn@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jack.bond-preston@foss.arm.com \
--cc=jerinj@marvell.com \
--cc=jianjay.zhou@huawei.com \
--cc=kai.ji@intel.com \
--cc=lee.daly@intel.com \
--cc=matan@nvidia.com \
--cc=maxime.coquelin@redhat.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=raveendra.padasalagi@broadcom.com \
--cc=ruifeng.wang@arm.com \
--cc=sunilprakashrao.uttarwar@amd.com \
--cc=vikas.gupta@broadcom.com \
--cc=zhangfei.gao@linaro.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).