From: Akhil Goyal <gakhil@marvell.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH v2 0/4] ipsec_mb fixes for ZUC algorithm
Date: Thu, 24 Feb 2022 10:23:00 +0000 [thread overview]
Message-ID: <CO6PR18MB4484DFA37B6F0B1E301A050ED83D9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220223160116.736804-1-pablo.de.lara.guarch@intel.com>
> This patchset fixes various issues affecting ZUC and AESNI MB PMD,
> when ZUC algorithm is used.
>
> -v2: rebased on main branch
>
> Pablo de Lara (4):
> crypto/ipsec_mb: check for missing operation types
> crypto/ipsec_mb: fix ZUC authentication verify
> crypto/ipsec_mb: fix crypto operation overwrite
> crypto/ipsec_mb: fix length and offset settings
>
> drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 122 +++++++++++++++++--------
> drivers/crypto/ipsec_mb/pmd_zuc.c | 22 +++--
> drivers/crypto/ipsec_mb/pmd_zuc_priv.h | 2 +-
> 3 files changed, 100 insertions(+), 46 deletions(-)
>
Series Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2022-02-24 10:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 16:34 [PATCH " Pablo de Lara
2022-02-18 16:34 ` [PATCH 1/4] crypto/ipsec_mb: check for missing operation types Pablo de Lara
2022-02-18 16:34 ` [PATCH 2/4] crypto/ipsec_mb: fix ZUC authentication verify Pablo de Lara
2022-02-18 16:34 ` [PATCH 3/4] crypto/ipsec_mb: fix crypto operation overwrite Pablo de Lara
2022-02-18 16:34 ` [PATCH 4/4] crypto/ipsec_mb: fix length and offset settings Pablo de Lara
2022-02-22 19:30 ` [EXT] " Akhil Goyal
2022-02-23 16:01 ` [PATCH v2 0/4] ipsec_mb fixes for ZUC algorithm Pablo de Lara
2022-02-23 16:01 ` [PATCH v2 1/4] crypto/ipsec_mb: check for missing operation types Pablo de Lara
2022-02-23 16:01 ` [PATCH v2 2/4] crypto/ipsec_mb: fix ZUC authentication verify Pablo de Lara
2022-02-23 16:01 ` [PATCH v2 3/4] crypto/ipsec_mb: fix crypto operation overwrite Pablo de Lara
2022-02-23 16:01 ` [PATCH v2 4/4] crypto/ipsec_mb: fix length and offset settings Pablo de Lara
2022-02-24 10:23 ` 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=CO6PR18MB4484DFA37B6F0B1E301A050ED83D9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@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).