From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v3] app/test/ipsec: fix test initialisation
Date: Fri, 5 Apr 2019 11:12:47 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772580148A937AE@irsmsx105.ger.corp.intel.com> (raw)
Message-ID: <20190405111247.6mlKR9tUPe-LtigRQ2SWDxjpFL8A-MJckubV6Uz8MiU@z> (raw)
In-Reply-To: <1554389511-6355-1-git-send-email-bernard.iremonger@intel.com>
>
> Fix xform initialisation.
> Fix testsuite_setup.
> Remove unused variables.
>
> Fixes: 05fe65eb66b2 ("test/ipsec: introduce functional test")
> Fixes: 59d7353b0df0 ("test/ipsec: fix test suite setup")
>
> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> ---
> Changes in v3:
> drop changes to logic around rte_cryptodev_dequeue_burst()
>
> app/test/test_ipsec.c | 34 +++++++++++++++-------------------
> 1 file changed, 15 insertions(+), 19 deletions(-)
>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> --
> 2.7.4
next prev parent reply other threads:[~2019-04-05 11:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 12:14 [dpdk-dev] [PATCH] test/ipsec: " Bernard Iremonger
2019-03-20 12:14 ` Bernard Iremonger
2019-03-22 13:47 ` [dpdk-dev] [PATCH v2] " Bernard Iremonger
2019-03-22 13:47 ` Bernard Iremonger
2019-03-22 14:20 ` Akhil Goyal
2019-03-22 14:20 ` Akhil Goyal
2019-04-04 13:54 ` Iremonger, Bernard
2019-04-04 13:54 ` Iremonger, Bernard
2019-04-04 14:51 ` [dpdk-dev] [PATCH v3] app/test/ipsec: " Bernard Iremonger
2019-04-04 14:51 ` Bernard Iremonger
2019-04-05 11:12 ` Ananyev, Konstantin [this message]
2019-04-05 11:12 ` Ananyev, Konstantin
2019-04-16 14:58 ` Akhil Goyal
2019-04-16 14:58 ` 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=2601191342CEEE43887BDE71AB9772580148A937AE@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@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).