DPDK patches and discussions
 help / color / mirror / Atom feed
From: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
To: dev@dpdk.org
Cc: alejandro.lucero@netronome.com, allain.legacy@windriver.com,
	jasvinder.singh@intel.com, keith.wiles@intel.com,
	matan@mellanox.com, bruce.richardson@intel.com,
	reshma.pattan@intel.com,
	Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
Subject: [dpdk-dev] [PATCH v4 0/6] fix for meson builds in freebsd
Date: Thu,  4 Oct 2018 15:09:57 +0100	[thread overview]
Message-ID: <1538662203-32585-1-git-send-email-agalyax.babu.radhakrishnan@intel.com> (raw)
In-Reply-To: <1538659944-18733-1>

Compilation issues were observed in FreeBSD when built via meson.
VFIO flags are enabled/disabled based on linux/freebsd.
Changes are done in meson.build files to ensure
the build of drivers are enabled/disabled based on platform.

1/6: set/unset of vfio flags based on platforms
2/6: updated net/nfp meson build
3/6: updated net/avp meson build
4/6: updated net/softnic meson build
5/6: updated net/tap meson build
6/6: updated net/vdev_netvsc meson build 

Signed-off-by: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>

--
v4: Added acked-by for required patches
v3: Updated with correct fixes line
v2: Added fixes line for the appropriate file
    Updated meson.build changes to config instead of lib
--

Agalya Babu RadhaKrishnan (6):
  build: fix for FREEBSD build via meson
  net/nfp: disable nfp build in FREEBSD
  net/avp: disable avp build in FREEBSD
  net/softnic: disable softnic build in FREEBSD
  net/tap: disable tap build in FREEBSD
  net/vdev_netvsc: disable vdev netvsc build in FREEBSD

 config/meson.build                  | 3 +++
 config/rte_config.h                 | 1 -
 drivers/net/avp/meson.build         | 3 +++
 drivers/net/nfp/meson.build         | 3 +++
 drivers/net/softnic/meson.build     | 3 +++
 drivers/net/tap/meson.build         | 3 +++
 drivers/net/vdev_netvsc/meson.build | 3 +++
 7 files changed, 18 insertions(+), 1 deletion(-)

-- 
2.13.6

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1538659944-18733-1>
2018-10-04 14:09 ` Agalya Babu RadhaKrishnan [this message]
2018-10-27 15:19   ` Thomas Monjalon
2018-10-04 14:09 ` [dpdk-dev] [PATCH v4 1/6] build: fix for FREEBSD build via meson Agalya Babu RadhaKrishnan
2018-10-04 14:09 ` [dpdk-dev] [PATCH v4 2/6] net/nfp: disable nfp build in FREEBSD Agalya Babu RadhaKrishnan
2018-10-04 14:10 ` [dpdk-dev] [PATCH v4 3/6] net/avp: disable avp " Agalya Babu RadhaKrishnan
2018-10-04 14:10 ` [dpdk-dev] [PATCH v4 4/6] net/softnic: disable softnic " Agalya Babu RadhaKrishnan
2018-10-04 14:10 ` [dpdk-dev] [PATCH v4 5/6] net/tap: disable tap " Agalya Babu RadhaKrishnan
2018-10-04 14:10 ` [dpdk-dev] [PATCH v4 6/6] net/vdev_netvsc: disable vdev netvsc " Agalya Babu RadhaKrishnan

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=1538662203-32585-1-git-send-email-agalyax.babu.radhakrishnan@intel.com \
    --to=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=keith.wiles@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).