DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] devtools: remove NFP from test-build
Date: Thu, 19 Jul 2018 12:11:52 +0100	[thread overview]
Message-ID: <CAD+H9912NJfzhVuYY5BNBnMwWxRW24TbAMo23nqVRHhktOaOzg@mail.gmail.com> (raw)
In-Reply-To: <20180719030331.32389-1-pablo.de.lara.guarch@intel.com>

On Thu, Jul 19, 2018 at 4:03 AM, Pablo de Lara <
pablo.de.lara.guarch@intel.com> wrote:

> NFP PMD does not have any external dependency.
> It only requires Linux OS, so it is not needed
> to be enabled in the test-build script.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
>  devtools/test-build.sh | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/devtools/test-build.sh b/devtools/test-build.sh
> index 3ea82bb46..f6db99fb0 100755
> --- a/devtools/test-build.sh
> +++ b/devtools/test-build.sh
> @@ -153,7 +153,6 @@ config () # <directory> <target> <options>
>                 sed -ri       's,(PMD_SZEDATA2=)n,\1y,' $1/.config
>                 test "$DPDK_DEP_ZLIB" != y || \
>                 sed -ri          's,(BNX2X_PMD=)n,\1y,' $1/.config
> -               sed -ri            's,(NFP_PMD=)n,\1y,' $1/.config
>                 test "$DPDK_DEP_PCAP" != y || \
>                 sed -ri               's,(PCAP=)n,\1y,' $1/.config
>                 test -z "$ARMV8_CRYPTO_LIB_PATH" || \
> --
> 2.14.4
>
>
Acked: Alejandro Lucero <alejandro.lucero@netronome.com>

  reply	other threads:[~2018-07-19 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19  3:03 Pablo de Lara
2018-07-19 11:11 ` Alejandro Lucero [this message]
2018-07-26  8:31   ` 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=CAD+H9912NJfzhVuYY5BNBnMwWxRW24TbAMo23nqVRHhktOaOzg@mail.gmail.com \
    --to=alejandro.lucero@netronome.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.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).