From: "Power, Ciara" <ciara.power@intel.com>
To: "Dooley, Brian" <brian.dooley@intel.com>,
"Ji, Kai" <kai.ji@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"Dooley, Brian" <brian.dooley@intel.com>
Subject: RE: [PATCH v1] crypto/ipsec_mb: use new ipad/opad calculation API
Date: Thu, 8 Feb 2024 16:15:15 +0000 [thread overview]
Message-ID: <SN7PR11MB7639428F9D617359C3926448E6442@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231214164135.2193863-1-brian.dooley@intel.com>
> -----Original Message-----
> From: Brian Dooley <brian.dooley@intel.com>
> Sent: Thursday, December 14, 2023 4:42 PM
> To: Ji, Kai <kai.ji@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; gakhil@marvell.com; Dooley, Brian
> <brian.dooley@intel.com>
> Subject: [PATCH v1] crypto/ipsec_mb: use new ipad/opad calculation API
>
> From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> IPSec Multi-buffer library v1.4 added a new API to calculate inner/outer
> padding for HMAC-SHAx/MD5.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> ---
> drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 34
> +++++++++++++++++++++++++-
> 1 file changed, 33 insertions(+), 1 deletion(-)
>
Acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2024-02-08 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 16:41 Brian Dooley
2024-02-08 16:15 ` Power, Ciara [this message]
2024-02-11 19:10 ` [PATCH v2] " Brian Dooley
2024-03-05 15:16 ` Wathsala Wathawana Vithanage
2024-06-05 8:48 [PATCH v1] " Brian Dooley
2024-06-10 8:19 ` Dooley, Brian
2024-06-20 9:00 ` Dooley, Brian
2024-06-24 14:33 ` Ji, Kai
2024-06-27 14:35 ` Wathsala Wathawana Vithanage
2024-07-03 17:26 ` Akhil Goyal
2024-07-02 13:32 ` Patrick Robb
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=SN7PR11MB7639428F9D617359C3926448E6442@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@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).