From: Akhil Goyal <akhil.goyal@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Fan Zhang <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
"arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] cryptodev: make xform key pointer constant
Date: Fri, 29 Mar 2019 16:01:50 +0000 [thread overview]
Message-ID: <e10f84bb-780c-2938-0969-f41d7be54b1d@nxp.com> (raw)
Message-ID: <20190329160150.uyug3oUI__Tnd3bF1ZHR8CkzsG5_YRrdFcP57XVvFwk@z> (raw)
In-Reply-To: <05939f96-106f-f7df-e7a7-4a75d66a1b8d@nxp.com>
On 3/29/2019 9:18 PM, Akhil Goyal wrote:
>
> On 3/29/2019 7:49 PM, Thomas Monjalon wrote:
>> 29/03/2019 15:07, Akhil Goyal:
>>> On 3/20/2019 7:02 PM, Fan Zhang wrote:
>>>> drivers/common/cpt/cpt_ucode.h | 14 ++---
>>>> drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 2 +-
>>>> drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 2 +-
>>>> drivers/crypto/openssl/rte_openssl_pmd.c | 8 +--
>>>> drivers/crypto/qat/qat_sym_session.c | 8 +--
>>>> drivers/crypto/qat/qat_sym_session.h | 4 +-
>>>> drivers/crypto/snow3g/rte_snow3g_pmd.c | 23 ++++++--
>>>> drivers/crypto/snow3g/rte_snow3g_pmd_private.h | 1 +
>>>> drivers/crypto/virtio/virtio_cryptodev.c | 30 +++++++---
>>>> drivers/crypto/virtio/virtio_cryptodev.h | 2 +
>>>> drivers/net/ixgbe/ixgbe_ipsec.c | 35 +++++++++---
>>>> drivers/net/ixgbe/ixgbe_ipsec.h | 3 +-
>>>> drivers/net/softnic/rte_eth_softnic_cli.c | 74 ++++++++++++-------------
>>>> drivers/net/softnic/rte_eth_softnic_internals.h | 4 ++
>>>> examples/ip_pipeline/cli.c | 74 ++++++++++++-------------
>>>> examples/ip_pipeline/cryptodev.c | 2 -
>>>> examples/ip_pipeline/pipeline.h | 6 ++
>>>> examples/l2fwd-crypto/main.c | 40 +++++--------
>>>> lib/librte_cryptodev/rte_crypto_sym.h | 12 ++--
>>>> 19 files changed, 190 insertions(+), 154 deletions(-)
>>>>
>>>>
>>> I believe this patch should be applied to master.
>>> This has changes for net and virtio pmds.
>> It's all related to crypto code, you can take it in the crypto tree.
> Ok..
> Applied to dpdk-next-crypto
This patch is taken back. As the changes introduce API breakage which
needs 1 release advance deprecation notice.
>
> Thanks.
>>> for librte_cryptodev, and l2fwd-crypto
>>>
>>> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
>>
next prev parent reply other threads:[~2019-03-29 16:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 13:43 [dpdk-dev] [PATCH] " Fan Zhang
2019-03-15 16:37 ` Kusztal, ArkadiuszX
2019-03-15 16:37 ` Kusztal, ArkadiuszX
2019-03-19 9:43 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2019-03-19 9:43 ` Fan Zhang
2019-03-20 13:32 ` [dpdk-dev] [PATCH v3] " Fan Zhang
2019-03-20 13:32 ` Fan Zhang
2019-03-20 17:28 ` Kusztal, ArkadiuszX
2019-03-20 17:28 ` Kusztal, ArkadiuszX
2019-03-29 14:07 ` Akhil Goyal
2019-03-29 14:07 ` Akhil Goyal
2019-03-29 14:19 ` Thomas Monjalon
2019-03-29 14:19 ` Thomas Monjalon
2019-03-29 15:48 ` Akhil Goyal
2019-03-29 15:48 ` Akhil Goyal
2019-03-29 16:01 ` Akhil Goyal [this message]
2019-03-29 16:01 ` Akhil Goyal
2019-05-28 9:52 ` Zhang, Roy Fan
2019-05-29 6:29 ` Akhil Goyal
2019-06-19 15:08 ` Akhil Goyal
2019-06-20 6:47 ` Thomas Monjalon
2019-06-24 13:35 ` [dpdk-dev] [PATCH v4] " Fan Zhang
2019-06-25 12:46 ` Akhil Goyal
2019-07-05 12:30 ` Thomas Monjalon
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=e10f84bb-780c-2938-0969-f41d7be54b1d@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=thomas@monjalon.net \
/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).