DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Marcin Smoczynski <marcinx.smoczynski@intel.com>
Cc: konstantin.ananyev@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ipsec: fix missing ipsec headers after install
Date: Wed, 8 May 2019 13:22:13 +0100	[thread overview]
Message-ID: <20190508122213.GA53@bricha3-MOBL.ger.corp.intel.com> (raw)
Message-ID: <20190508122213.Nlz1EesVkoZzQQqJ-Vg6AZkMNYFn1q-0GczY5IRF2V8@z> (raw)
In-Reply-To: <20190508121212.15940-1-marcinx.smoczynski@intel.com>

On Wed, May 08, 2019 at 02:12:12PM +0200, Marcin Smoczynski wrote:
> Invalid statement is used to indicate header files to install.
> 
> Fixed the statement and reformatted recipe file.
> 
> Signed-off-by: Marcin Smoczynski <marcinx.smoczynski@intel.com>
> ---
>  lib/librte_ipsec/meson.build | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/librte_ipsec/meson.build b/lib/librte_ipsec/meson.build
> index 18fb2a143..7ea0c7dbb 100644
> --- a/lib/librte_ipsec/meson.build
> +++ b/lib/librte_ipsec/meson.build
> @@ -3,8 +3,8 @@
>  
>  allow_experimental_apis = true
>  
> -sources=files('esp_inb.c', 'esp_outb.c', 'sa.c', 'ses.c')
> +sources = files('esp_inb.c', 'esp_outb.c', 'sa.c', 'ses.c')
>  
> -install_headers = files('rte_ipsec.h', 'rte_ipsec_group.h', 'rte_ipsec_sa.h')
> +headers = files('rte_ipsec.h', 'rte_ipsec_group.h', 'rte_ipsec_sa.h')
>  
>  deps += ['mbuf', 'net', 'cryptodev', 'security']

Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  parent reply	other threads:[~2019-05-08 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 12:12 Marcin Smoczynski
2019-05-08 12:12 ` Marcin Smoczynski
2019-05-08 12:22 ` Bruce Richardson [this message]
2019-05-08 12:22   ` Bruce Richardson
2019-05-09 13:22   ` Thomas Monjalon
2019-05-09 13:22     ` 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=20190508122213.GA53@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=marcinx.smoczynski@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).