DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>,
	"Power, Ciara" <ciara.power@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 0/3] cryptodev test improvements
Date: Thu, 16 Mar 2023 18:16:12 +0000	[thread overview]
Message-ID: <CO6PR18MB44843620B388BA9FC34A8A22D8BC9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB3408B5FE090910799546A5B281B79@SN6PR11MB3408.namprd11.prod.outlook.com>

> Acked-by: Kai Ji <kai.ji@intel.com>
> 
> > Subject: [PATCH 0/3] cryptodev test improvements
> >
> > The meson driver-tests suite was missing some QAT and SW PMD crypto
> > tests, which are now added.
> >
> > Some issues were highlighted after adding to the driver-tests suite,
> > which are also addressed in this patchset.
Applied to dpdk-next-crypto

Thanks

  reply	other threads:[~2023-03-16 18:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 17:17 Ciara Power
2023-03-07 17:17 ` [PATCH 1/3] test/crypto: fix skip condition for CPU crypto SGL Ciara Power
2023-03-07 17:43   ` Ji, Kai
2023-03-07 17:17 ` [PATCH 2/3] test/crypto: skip asym test if driver or device missing Ciara Power
2023-03-07 17:17 ` [PATCH 3/3] app/test: add more cryptodev tests to meson suite Ciara Power
2023-03-07 17:23   ` [EXT] " Akhil Goyal
2023-03-07 17:32     ` Power, Ciara
2023-03-07 17:42       ` Akhil Goyal
2023-03-07 17:43 ` [PATCH 0/3] cryptodev test improvements Ji, Kai
2023-03-16 18:16   ` Akhil Goyal [this message]
2023-03-07 17:46 ` Ji, Kai

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=CO6PR18MB44843620B388BA9FC34A8A22D8BC9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@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).