patches for DPDK stable branches
 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>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] app/test/ipsec: fix logic around dequeue burst
Date: Wed, 17 Apr 2019 08:59:25 +0000	[thread overview]
Message-ID: <VI1PR04MB4893D3F93D39F46B9D24AA7AE6250@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VI1PR04MB489382CAC3F2426F0C183CF1E6250@VI1PR04MB4893.eurprd04.prod.outlook.com>

> >
> > Added crypto_dequeue_burst() function to call
> > rte_crypto_dequeue_burst() in a loop with a
> > delay to ensure that all the  packets are
> > dequeued from the crtpto device.
> >
> > Fixes: 59d7353b0df0 ("test/ipsec: fix test suite setup")
> > Cc: stable@dpdk.org
> > Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> > Acked-by: Fiona Trahe <fiona.trahe@intel.com>
> > Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> > ---
> > Changes in v2:
> > Added crypto_dequeue_burst() function
> >
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied to dpdk-next-crypto

Thanks.


  reply	other threads:[~2019-04-17  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17  8:54 Akhil Goyal
2019-04-17  8:59 ` Akhil Goyal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-11 13:08 [dpdk-stable] [PATCH] " Bernard Iremonger
2019-04-12 14:08 ` [dpdk-stable] [PATCH v2] " 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=VI1PR04MB4893D3F93D39F46B9D24AA7AE6250@VI1PR04MB4893.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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).