DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] test/crypto: fix compilation issue without security
Date: Wed, 23 Oct 2019 14:48:10 +0000	[thread overview]
Message-ID: <VE1PR04MB6639657C8F47C95BB8D06F92E66B0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <89e20661-e08c-09a6-4c84-971da2ea6b33@6wind.com>



> On 10/18/19 9:56 AM, Hemant Agrawal wrote:
> > This patch fixes the compilation issue in test_cryptodev.c
> > when RTE_LIBRTE_SECURITY is disabled.
> > Fixes: d883e6e7131b ("test/crypto: add PDCP C-Plane encap cases")
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > ---
> >   app/test/test_cryptodev.c | 9 ++++++++-
> >   1 file changed, 8 insertions(+), 1 deletion(-)
> >
> 
> Acked-by: Thierry Herbelot <thierry.herbelot@6wind.com>
> 
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2019-10-23 14:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  7:56 Hemant Agrawal
2019-10-18  7:56 ` [dpdk-dev] [PATCH] app/proc-info: fix compilation with no security Hemant Agrawal
2019-10-18  8:09   ` Thierry Herbelot
2019-10-23 14:46     ` Akhil Goyal
2019-10-23 14:48     ` Akhil Goyal
2019-10-18  7:56 ` [dpdk-dev] [PATCH] crypto/dpaa_sec: enable compilation without security Hemant Agrawal
2019-10-18  8:11   ` Thierry Herbelot
2019-10-23 14:45   ` Akhil Goyal
2019-10-18  8:07 ` [dpdk-dev] [PATCH] test/crypto: fix compilation issue " Thierry Herbelot
2019-10-23 14:48   ` 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=VE1PR04MB6639657C8F47C95BB8D06F92E66B0@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=thierry.herbelot@6wind.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).