From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Drost, MariuszX" <mariuszx.drost@intel.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Drost, MariuszX" <mariuszx.drost@intel.com>
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: enable cpu-crypto fallback
Date: Mon, 23 Mar 2020 12:47:39 +0000 [thread overview]
Message-ID: <SN6PR11MB25586B05E050AD6667DDDCDB9AF00@SN6PR11MB2558.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200318132659.1031-1-mariuszx.drost@intel.com>
>
> Added cpu-crypto fallback option parsing as well as tests for it
>
> Signed-off-by: Mariusz Drost <mariuszx.drost@intel.com>
> ---
Tested-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.17.1
next prev parent reply other threads:[~2020-03-23 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 13:26 Mariusz Drost
2020-03-23 12:47 ` Ananyev, Konstantin [this message]
2020-04-05 16:59 ` 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=SN6PR11MB25586B05E050AD6667DDDCDB9AF00@SN6PR11MB2558.namprd11.prod.outlook.com \
--to=konstantin.ananyev@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=mariuszx.drost@intel.com \
--cc=radu.nicolau@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).