DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Babu Radhakrishnan, AgalyaX" <agalyax.babu.radhakrishnan@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"alejandro.lucero@netronome.com" <alejandro.lucero@netronome.com>,
	"allain.legacy@windriver.com" <allain.legacy@windriver.com>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>,
	"matan@mellanox.com" <matan@mellanox.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 5/6] net/tap: disable tap build in FREEBSD
Date: Wed, 3 Oct 2018 14:24:09 +0000	[thread overview]
Message-ID: <833D4A94-FB7A-44D8-B31C-C6B4862B8BEE@intel.com> (raw)
In-Reply-To: <1538575221-23873-6-git-send-email-agalyax.babu.radhakrishnan@intel.com>



> On Oct 3, 2018, at 9:00 AM, Babu Radhakrishnan, AgalyaX <agalyax.babu.radhakrishnan@intel.com> wrote:
> 
> Disabled tap build in FreeBSD because it is not supported
> Added changes to enable tap build if it is Linux OS and
> disable in FreeBSD.
> 
> Signed-off-by: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>

Thought I acked this one already.

Acked-by: Keith Wiles <keith.wiles@intel.com>

> ---
> drivers/net/tap/meson.build | 3 +++
> 1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/net/tap/meson.build b/drivers/net/tap/meson.build
> index 37f65b75c..5d30cd52d 100644
> --- a/drivers/net/tap/meson.build
> +++ b/drivers/net/tap/meson.build
> @@ -1,6 +1,9 @@
> # SPDX-License-Identifier: BSD-3-Clause
> # Copyright 2018 Luca Boccassi <bluca@debian.org>
> 
> +if host_machine.system() != 'linux'
> +        build = false
> +endif
> sources = files(
> 	'rte_eth_tap.c',
> 	'tap_bpf_api.c',
> -- 
> 2.13.6
> 

Regards,
Keith

  reply	other threads:[~2018-10-03 14:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1538054652-20820-1>
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 0/6] fix for meson builds in freebsd Agalya Babu RadhaKrishnan
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 1/6] build: fix for FREEBSD build via meson Agalya Babu RadhaKrishnan
2018-10-03 15:42   ` Bruce Richardson
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 2/6] net/nfp: disable nfp build in FREEBSD Agalya Babu RadhaKrishnan
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 3/6] net/avp: disable avp " Agalya Babu RadhaKrishnan
2018-10-03 15:12   ` Legacy, Allain
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 4/6] net/softnic: disable softnic " Agalya Babu RadhaKrishnan
2018-10-03 15:36   ` Singh, Jasvinder
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 5/6] net/tap: disable tap " Agalya Babu RadhaKrishnan
2018-10-03 14:24   ` Wiles, Keith [this message]
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 6/6] net/vdev_netvsc: disable vdev netvsc " Agalya Babu RadhaKrishnan
2018-10-03 15:10   ` Stephen Hemminger
     [not found] ` <1538574386-21771-2-git-send-email-agalyabx@wgcvswdev001.ir.intel.com>
2018-10-03 15:33   ` [dpdk-dev] [PATCH v2 1/6] build: fix for FREEBSD build via meson Bruce Richardson

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=833D4A94-FB7A-44D8-B31C-C6B4862B8BEE@intel.com \
    --to=keith.wiles@intel.com \
    --cc=agalyax.babu.radhakrishnan@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=allain.legacy@windriver.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --cc=matan@mellanox.com \
    --cc=reshma.pattan@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).