DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Bernard Iremonger <bernard.iremonger@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] test/ipsec: fixes and improvements
Date: Tue, 25 Jun 2019 12:48:56 +0000	[thread overview]
Message-ID: <VE1PR04MB66399F1351603D53E983D664E6E30@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1559903595-18506-1-git-send-email-bernard.iremonger@intel.com>



> 
> The following patches contain one fix and
> improvements to test_ipsec.c
> 
> Changes in v2:
> -------------
> Patch 1 has been dropped as it hides the issue with QAT PMD.
> Patch 3 has been dropped as the hang issue with QAT device is not occurring
> with the latest DPDK 18.08 code.
> The commit message for patch 5 has been changed, now patch 3.
> 
> Bernard Iremonger (3):
>   test/ipsec: fix log messages in tests
>   test/ipsec: add extra test configuration
>   test/ipsec: improve debug in group tests
> 
>  app/test/test_ipsec.c | 67 +++++++++++++++++++++++++--------------------------
>  1 file changed, 33 insertions(+), 34 deletions(-)
> 
> --
> 2.7.4
Series Applied to dpdk-next-crypto

Thanks.

  parent reply	other threads:[~2019-06-25 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1558532302-15932-0-git-send-email-bernard.iremonger@intel.com>
2019-06-07 10:33 ` Bernard Iremonger
2019-06-11 16:20   ` Ananyev, Konstantin
2019-06-25 12:48   ` Akhil Goyal [this message]
2019-06-07 10:33 ` [dpdk-dev] [PATCH v2 1/3] test/ipsec: fix log messages in tests Bernard Iremonger
2019-06-07 10:33 ` [dpdk-dev] [PATCH v2 2/3] test/ipsec: add extra test configuration Bernard Iremonger
2019-06-07 10:33 ` [dpdk-dev] [PATCH v2 3/3] test/ipsec: improve debug in group tests Bernard Iremonger

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=VE1PR04MB66399F1351603D53E983D664E6E30@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).