DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>,
	"ravi1.kumar@amd.com" <ravi1.kumar@amd.com>,
	"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
	"anoobj@marvell.com" <anoobj@marvell.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	"tdu@semihalf.com" <tdu@semihalf.com>,
	"rnagadheeraj@marvell.com" <rnagadheeraj@marvell.com>,
	"adwivedi@marvell.com" <adwivedi@marvell.com>,
	"g.singh@nxp.com" <g.singh@nxp.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"jianjay.zhou@huawei.com" <jianjay.zhou@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 3/4] test/crypto: check if device supports	out-of-place ops
Date: Thu, 16 Apr 2020 13:41:31 +0000	[thread overview]
Message-ID: <BY5PR11MB391071D4575CCBE7B87ED295EDD80@BY5PR11MB3910.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200416092532.1922099-4-pablo.de.lara.guarch@intel.com>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Pablo de Lara
> Sent: Thursday, 16 April, 2020 11:26
> To: Doherty, Declan <declan.doherty@intel.com>; ravi1.kumar@amd.com;
> ruifeng.wang@arm.com; anoobj@marvell.com; Zhang, Roy Fan
> <roy.fan.zhang@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>;
> tdu@semihalf.com; rnagadheeraj@marvell.com; adwivedi@marvell.com;
> g.singh@nxp.com; hemant.agrawal@nxp.com; jianjay.zhou@huawei.com
> Cc: dev@dpdk.org; akhil.goyal@nxp.com; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Subject: [dpdk-dev] [PATCH v2 3/4] test/crypto: check if device supports out-
> of-place ops
> 
> Before running any out-of-place test cases, check if device supports this
> mode.
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

Acked-by: Adam Dybkowski <adamx.dybkowski@intel.com>


  reply	other threads:[~2020-04-16 13:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 18:04 [dpdk-dev] [PATCH 0/3] Crypto test refactoring (second phase) Pablo de Lara
2020-04-14 18:04 ` [dpdk-dev] [PATCH 1/3] cryptodev: add sessionless support feature flag Pablo de Lara
2020-04-15 10:38   ` Dybkowski, AdamX
2020-04-14 18:04 ` [dpdk-dev] [PATCH 2/3] test/crypto: check if device supports sessionless Pablo de Lara
2020-04-15 10:38   ` Dybkowski, AdamX
2020-04-14 18:04 ` [dpdk-dev] [PATCH 3/3] test/crypto: do not check for PMD in tests Pablo de Lara
2020-04-15 10:38   ` Dybkowski, AdamX
2020-04-16  8:28 ` [dpdk-dev] [PATCH 0/3] Crypto test refactoring (second phase) Ruifeng Wang
2020-04-16 13:28   ` De Lara Guarch, Pablo
2020-04-16 15:23     ` Ruifeng Wang
2020-04-16  9:25 ` [dpdk-dev] [PATCH v2 0/4] " Pablo de Lara
2020-04-16  9:25   ` [dpdk-dev] [PATCH v2 1/4] cryptodev: add sessionless support feature flag Pablo de Lara
2020-04-16 15:27     ` Ruifeng Wang
2020-04-16  9:25   ` [dpdk-dev] [PATCH v2 2/4] test/crypto: check if device supports sessionless Pablo de Lara
2020-04-16 15:27     ` Ruifeng Wang
2020-04-16  9:25   ` [dpdk-dev] [PATCH v2 3/4] test/crypto: check if device supports out-of-place ops Pablo de Lara
2020-04-16 13:41     ` Dybkowski, AdamX [this message]
2020-04-16 15:28     ` Ruifeng Wang
2020-04-16  9:25   ` [dpdk-dev] [PATCH v2 4/4] test/crypto: do not check for PMD in tests Pablo de Lara
2020-04-16 15:28     ` Ruifeng Wang
2020-04-16 16:52   ` [dpdk-dev] [PATCH v2 0/4] Crypto test refactoring (second phase) Trahe, Fiona
2020-04-19 21:13     ` Akhil Goyal

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=BY5PR11MB391071D4575CCBE7B87ED295EDD80@BY5PR11MB3910.namprd11.prod.outlook.com \
    --to=adamx.dybkowski@intel.com \
    --cc=adwivedi@marvell.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=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=ravi1.kumar@amd.com \
    --cc=rnagadheeraj@marvell.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=ruifeng.wang@arm.com \
    --cc=tdu@semihalf.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).