DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thierry.herbelot@6wind.com" <thierry.herbelot@6wind.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/dpaa_sec: enable compilation without security
Date: Wed, 23 Oct 2019 14:45:11 +0000	[thread overview]
Message-ID: <VE1PR04MB6639412AD1C726BCC68E6209E66B0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20191018075613.2784-3-hemant.agrawal@nxp.com>



> 
> This patch enables the dpaaX_sec compilation when SECURITY
> is disabled.
> 
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
>  drivers/crypto/Makefile                     |  4 ++--
>  drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 26 +++++++++++++++------
>  drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h   | 11 +++++++--
>  drivers/crypto/dpaa_sec/dpaa_sec.c          | 25 ++++++++++++++------
>  drivers/crypto/dpaa_sec/dpaa_sec.h          | 10 ++++++--
>  mk/rte.app.mk                               |  4 ++--
>  6 files changed, 58 insertions(+), 22 deletions(-)
> 
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied to dpdk-next-crypto

Thanks.

Certain ifdefs were not placed correctly. Fixed those while applying the series.

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  7:56 [dpdk-dev] [PATCH] test/crypto: fix compilation issue " 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 [this message]
2019-10-18  8:07 ` [dpdk-dev] [PATCH] test/crypto: fix compilation issue " Thierry Herbelot
2019-10-23 14:48   ` 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=VE1PR04MB6639412AD1C726BCC68E6209E66B0@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).