From: Xiao Wang <xiao.w.wang@intel.com>
To: ferruh.yigit@intel.com
Cc: dev@dpdk.org, bruce.richardson@intel.com,
Xiao Wang <xiao.w.wang@intel.com>
Subject: [dpdk-dev] [PATCH 2/2] net/ifc: add to meson build
Date: Wed, 13 Jun 2018 19:32:46 +0800 [thread overview]
Message-ID: <20180613113246.13576-3-xiao.w.wang@intel.com> (raw)
In-Reply-To: <20180613113246.13576-1-xiao.w.wang@intel.com>
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
---
drivers/net/ifc/meson.build | 7 +++++++
drivers/net/meson.build | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
create mode 100644 drivers/net/ifc/meson.build
diff --git a/drivers/net/ifc/meson.build b/drivers/net/ifc/meson.build
new file mode 100644
index 000000000..a30aa09e6
--- /dev/null
+++ b/drivers/net/ifc/meson.build
@@ -0,0 +1,7 @@
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2018 Intel Corporation
+
+allow_experimental_apis = true
+sources = files('ifcvf_vdpa.c', 'base/ifcvf.c')
+includes += include_directories('base')
+deps += 'vhost'
diff --git a/drivers/net/meson.build b/drivers/net/meson.build
index b7d00a04c..2042859c1 100644
--- a/drivers/net/meson.build
+++ b/drivers/net/meson.build
@@ -2,7 +2,7 @@
# Copyright(c) 2017 Intel Corporation
drivers = ['af_packet', 'axgbe', 'bonding', 'dpaa', 'dpaa2',
- 'e1000', 'enic', 'fm10k', 'i40e', 'ixgbe',
+ 'e1000', 'enic', 'fm10k', 'i40e', 'ifc', 'ixgbe',
'mvpp2', 'null', 'octeontx', 'pcap', 'ring',
'sfc', 'thunderx', 'virtio']
std_deps = ['ethdev', 'kvargs'] # 'ethdev' also pulls in mbuf, net, eal etc
--
2.15.1
next prev parent reply other threads:[~2018-06-13 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 11:32 [dpdk-dev] [PATCH 0/2] add ifc driver " Xiao Wang
2018-06-13 11:32 ` [dpdk-dev] [PATCH 1/2] net/ifc: make driver name consistent Xiao Wang
2018-06-13 11:32 ` Xiao Wang [this message]
2018-06-14 11:52 ` [dpdk-dev] [PATCH 0/2] add ifc driver to meson build Ferruh Yigit
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=20180613113246.13576-3-xiao.w.wang@intel.com \
--to=xiao.w.wang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).