patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Adam Dybkowski <adamx.dybkowski@intel.com>,
	Akhil Goyal <akhil.goyal@nxp.com>
Cc: Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2 1/1] test/crypto: fix missing operation status	check
Date: Fri, 17 Jan 2020 17:21:53 +0100	[thread overview]
Message-ID: <4701288.e8TTKsaY2g@xps> (raw)
In-Reply-To: <VE1PR04MB66394B912F9D678FDEB47A5AE6370@VE1PR04MB6639.eurprd04.prod.outlook.com>

15/01/2020 16:54, Akhil Goyal:
> > >
> > > Fixes: c0f87eb5252b ("cryptodev: change burst API to be crypto op oriented")
> > > Fixes: 77a217a19bb7 ("test/crypto: add AES-CCM tests")
> > >
> > > Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> > > ---
> > >  app/test/test_cryptodev.c | 96 +++++++++++++++++++++------------------
> > >  1 file changed, 52 insertions(+), 44 deletions(-)
> > >
> > 
> > Tested-by: Ankur Dwivedi <adwivedi@marvell.com>
> > Reviewed-by: Anoob Joseph <anoobj@marvell.com>
> 
> Applied to dpdk-next-crypto

Cc: stable@dpdk.org is missing
I guess you want to backport it so I add the tag in master.



      reply	other threads:[~2020-01-17 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191220115004.2713-1-adamx.dybkowski@intel.com>
2019-12-20 12:58 ` [dpdk-stable] [PATCH v2 0/1] " Adam Dybkowski
2019-12-20 12:58   ` [dpdk-stable] [PATCH v2 1/1] " Adam Dybkowski
2019-12-20 13:06     ` Trahe, Fiona
2020-01-10 10:54     ` [dpdk-stable] [dpdk-dev] " Anoob Joseph
2020-01-15 15:54       ` Akhil Goyal
2020-01-17 16:21         ` Thomas Monjalon [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=4701288.e8TTKsaY2g@xps \
    --to=thomas@monjalon.net \
    --cc=adamx.dybkowski@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.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).