From: Thomas Monjalon <thomas@monjalon.net>
To: Anoob Joseph <anoobj@marvell.com>,
Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
bluca@debian.org, ktraynor@redhat.com, david.marchand@redhat.com,
nhorman@tuxdriver.com, ray.kinsella@intel.com,
ferruh.yigit@intel.com, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v3] cryptodev: add chacha20-poly1305 aead algorithm
Date: Wed, 05 Feb 2020 15:28:56 +0100 [thread overview]
Message-ID: <2631430.Y6S9NjorxK@xps> (raw)
In-Reply-To: <VE1PR04MB66395982EAEDB7E24E63E605E6370@VE1PR04MB6639.eurprd04.prod.outlook.com>
15/01/2020 16:53, Akhil Goyal:
> > > This patch adds Chacha20-Poly1305 AEAD algorithm to Cryptodev.
> > >
> > > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> > > Acked-by: Fiona Trahe <fiona.trahe@intel.com>
> >
> > Acked-by: Anoob Joseph <anoobj@marvell.com>
> >
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
>
> Applied to dpdk-next-crypto
As discussed in other email threads,
this patch was causing an ABI breakage and had to be reverted:
http://git.dpdk.org/dpdk/commit/?id=f5862ae99
Sorry, this feature will miss 20.02 release I'm afraid.
2 actions should be taken:
- try to re-intoduce the feature with function versioning
- improve ABI stability in DPDK 20.11 for future features
We are all (hardly) learning how to maintain ABI compatibility,
as this is our first real issue since the new ABI policy.
Thanks for understanding.
next prev parent reply other threads:[~2020-02-05 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 10:43 Arek Kusztal
2020-01-14 12:49 ` Trahe, Fiona
2020-01-14 12:52 ` Trahe, Fiona
2020-01-14 13:18 ` Anoob Joseph
2020-01-15 15:53 ` Akhil Goyal
2020-02-05 14:28 ` Thomas Monjalon [this message]
2020-02-05 14:41 ` Trahe, Fiona
2020-02-05 15:21 ` Thomas Monjalon
2020-04-17 15:43 Arek Kusztal
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=2631430.Y6S9NjorxK@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.com \
--cc=ktraynor@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=pathreya@marvell.com \
--cc=ray.kinsella@intel.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).