From: Akhil Goyal <akhil.goyal@nxp.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Coyle, David" <david.coyle@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Ryan, Brendan" <brendan.ryan@intel.com>,
"O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1 2/2] app/crypto-perf: enable security feature for security tests
Date: Sat, 18 Jul 2020 20:08:57 +0000 [thread overview]
Message-ID: <VI1PR04MB3168CB925C521DECFB84B8A3E67D0@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB3101191CE2735A53EDFBC4A6847C0@SN6PR11MB3101.namprd11.prod.outlook.com>
> > The RTE_CRYPTODEV_FF_SECURITY feature was disabled through the
> ff_disable
> > device configuration option for all crypto performance tests, including security
> > related tests. This patch updates the crypto performance tool to not disable
> > RTE_CRYPTODEV_FF_SECURITY for DOCSIS and PDCP security tests.
> >
> > Fixes: d4a131a9498d ("test/crypto-perf: support DOCSIS protocol")
> >
> > Signed-off-by: David Coyle <david.coyle@intel.com>
>
> Same comment as on the first patch of this set, but with commit 8fd2b5a60d1
> ("app/crypto-perf: support PDCP")
>
No need to backport this as well as explained in the 1st patch.
prev parent reply other threads:[~2020-07-18 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 15:29 [dpdk-dev] [PATCH v1 0/2] " David Coyle
2020-07-16 15:29 ` [dpdk-dev] [PATCH v1 1/2] test/crypto: " David Coyle
2020-07-16 17:05 ` Akhil Goyal
2020-07-18 21:18 ` Akhil Goyal
2020-07-17 18:17 ` De Lara Guarch, Pablo
2020-07-18 20:07 ` Akhil Goyal
2020-07-16 15:29 ` [dpdk-dev] [PATCH v1 2/2] app/crypto-perf: " David Coyle
2020-07-16 17:01 ` Akhil Goyal
2020-07-17 18:19 ` De Lara Guarch, Pablo
2020-07-18 20:08 ` Akhil Goyal [this message]
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=VI1PR04MB3168CB925C521DECFB84B8A3E67D0@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=brendan.ryan@intel.com \
--cc=david.coyle@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=mairtin.oloingsigh@intel.com \
--cc=pablo.de.lara.guarch@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).