DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anoob Joseph <anoobj@marvell.com>
To: Archana Muniganti <marchana@marvell.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: Archana Muniganti <marchana@marvell.com>,
	Sucharitha Sarananaga <ssarananaga@marvell.com>,
	Sunila Sahu <ssahu@marvell.com>,
	Shally Verma <shallyv@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Narayana Prasad Raju Athreya <pathreya@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/6] common/cpt: code improvements and bug fixes
Date: Sun, 2 Feb 2020 06:14:45 +0000	[thread overview]
Message-ID: <MN2PR18MB28771A9C3EF31E3213C906A6DF010@MN2PR18MB2877.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1580571769-7042-1-git-send-email-marchana@marvell.com>

>
> This series has code improvements, bug fixes and capabilities changes supported
> with new firmware.
> 
> Anoob Joseph (1):
>   common/cpt: remove redundant bitswaps
> 
> Archana Muniganti (3):
>   crypto/octeontx2: add AES-GCM capabilities supported with new firmware
>   common/cpt: fix error path when cipher and auth key are not set
>   common/cpt: fix fill_sg_comp api for zero datalen
> 
> Sucharitha Sarananaga (1):
>   common/cpt: support variable key size for HMAC
> 
> Sunila Sahu (1):
>   common/cpt: removes self assignment code
> 
>  drivers/common/cpt/cpt_mcode_defines.h             | 47 +++--------
>  drivers/common/cpt/cpt_ucode.h                     | 91 +++++++++++-----------
>  drivers/common/cpt/cpt_ucode_asym.h                |  1 -
>  .../crypto/octeontx/otx_cryptodev_capabilities.c   | 30 +++----
>  .../crypto/octeontx2/otx2_cryptodev_capabilities.c | 34 ++++----
>  5 files changed, 87 insertions(+), 116 deletions(-)
> 
> --
> 1.8.3.1

Series Acked-by: Anoob Joseph <anoobj@marvell.com>

           reply	other threads:[~2020-02-02  6:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1580571769-7042-1-git-send-email-marchana@marvell.com>]

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=MN2PR18MB28771A9C3EF31E3213C906A6DF010@MN2PR18MB2877.namprd18.prod.outlook.com \
    --to=anoobj@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=marchana@marvell.com \
    --cc=pathreya@marvell.com \
    --cc=shallyv@marvell.com \
    --cc=ssahu@marvell.com \
    --cc=ssarananaga@marvell.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).