patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Gagandeep Singh <G.Singh@nxp.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Fan Zhang <royzhang1980@gmail.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] test/cryptodev: fix PDCP vectors
Date: Fri, 21 Oct 2022 15:04:18 +0000	[thread overview]
Message-ID: <PH0PR18MB449147B90752BEBE8991A2CFD82D9@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <AS8PR04MB819859EFF027DE25FCCC7824E1259@AS8PR04MB8198.eurprd04.prod.outlook.com>

> > Subject: [PATCH] test/cryptodev: fix PDCP vectors
> >
> > The existing PDCP vectors have a deviation from the PDCP header
> > specification. The reserved fields are set to 0 in the PDCP headers and
> > D/C bits are updated as per the use case. The MAC-I for the
> > corresponding vectors are also updated.
> >
> > Fixes: d883e6e7131b ("test/crypto: add PDCP C-Plane encap cases")
> > Fixes: cca7d1f78524 ("test/crypto: add PDCP U-Plane encap with integrity
> > cases")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> Tested-by: Gagandeep Singh <g.singh@nxp.com>
> 
> Verified the patch on DPAA2 platform.

Acked-by: Akhil Goyal <gakhil@marvell.com>

Applied to dpdk-next-crypto

Thanks.


      reply	other threads:[~2022-10-21 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13  3:59 Anoob Joseph
2022-10-13  7:21 ` Gagandeep Singh
2022-10-21 15:04   ` 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=PH0PR18MB449147B90752BEBE8991A2CFD82D9@PH0PR18MB4491.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=G.Singh@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=royzhang1980@gmail.com \
    --cc=stable@dpdk.org \
    /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).