DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Radu Nicolau <radu.nicolau@intel.com>, <dev@dpdk.org>
Cc: <david.marchand@6wind.com>, <declan.doherty@intel.com>,
	<pablo.de.lara.guarch@intel.com>, <hemant.agrawal@nxp.com>,
	<borisp@mellanox.com>, <aviadye@mellanox.com>,
	<thomas@monjalon.net>, <sandeep.malik@nxp.com>,
	<jerin.jacob@caviumnetworks.com>, <john.mcnamara@intel.com>,
	<konstantin.ananyev@intel.com>, <shahafs@mellanox.com>,
	<olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] Build fails when rte_security is disabled.
Date: Thu, 26 Oct 2017 16:01:57 +0530	[thread overview]
Message-ID: <3c62a0eb-2fa9-ea1a-e876-7a9e6c8da5ca@nxp.com> (raw)
In-Reply-To: <1509013365-13819-1-git-send-email-radu.nicolau@intel.com>

On 10/26/2017 3:52 PM, Radu Nicolau wrote:
> Disabling CONFIG_RTE_LIBRTE_SECURITY results in build failure for
> crypto/dpaa2_sec and net/ixgbe PMDs and IPsec sample app.
> This patchset makes CONFIG_RTE_LIBRTE_SECURITY mandatory for all
> of the above.
> 
> Radu Nicolau (3):
>    crypto/dpaa2_sec: fix build issue
>    net/ixgbe: fix build issue
>    examples/ipsec-secgw: fix build issue
> 
>   drivers/crypto/dpaa2_sec/Makefile | 6 ++++++
>   drivers/net/ixgbe/Makefile        | 6 ++++++
>   examples/ipsec-secgw/Makefile     | 6 ++++++
>   3 files changed, 18 insertions(+)
> 
Series Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

  parent reply	other threads:[~2017-10-26 10:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 10:22 Radu Nicolau
2017-10-26 10:22 ` [dpdk-dev] [PATCH 1/3] crypto/dpaa2_sec: fix build issue Radu Nicolau
2017-10-26 10:22 ` [dpdk-dev] [PATCH 2/3] net/ixgbe: " Radu Nicolau
2017-10-26 10:36   ` David Marchand
2017-10-26 11:01     ` Radu Nicolau
2017-10-26 11:27       ` David Marchand
2017-10-26 11:39         ` Thomas Monjalon
2017-10-26 12:28           ` Radu Nicolau
2017-10-26 12:33             ` Thomas Monjalon
2017-10-26 12:59               ` Akhil Goyal
2017-10-26 13:07                 ` Thomas Monjalon
2017-10-26 13:16                   ` Akhil Goyal
2017-10-26 14:00                     ` Thomas Monjalon
2017-10-26 11:30       ` Ananyev, Konstantin
2017-10-26 11:39         ` David Marchand
2017-10-26 12:30           ` Radu Nicolau
2017-10-26 12:33           ` Ananyev, Konstantin
2017-10-26 10:22 ` [dpdk-dev] [PATCH 3/3] examples/ipsec-secgw: " Radu Nicolau
2017-10-26 10:31 ` Akhil Goyal [this message]
2017-10-26 14:15 ` [dpdk-dev] [PATCH v2 0/3] Build fails when rte_security is disabled Radu Nicolau
2017-10-26 14:15   ` [dpdk-dev] [PATCH v2 1/3] net/ixgbe: fix build issue Radu Nicolau
2017-10-26 14:15   ` [dpdk-dev] [PATCH v2 2/3] examples/ipsec-secgw: " Radu Nicolau
2017-10-26 14:15   ` [dpdk-dev] [PATCH v2 3/3] crypto/dpaa2_sec: " Radu Nicolau
2017-10-26 15:27   ` [dpdk-dev] [PATCH v2 0/3] Build fails when rte_security is disabled David Marchand
2017-10-26 20:36     ` Thomas Monjalon

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=3c62a0eb-2fa9-ea1a-e876-7a9e6c8da5ca@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=david.marchand@6wind.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.mcnamara@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=radu.nicolau@intel.com \
    --cc=sandeep.malik@nxp.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    /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).