DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
To: bruce.richardson@intel.com, jerin.jacob@caviumnetworks.com,
	santosh.shukla@caviumnetworks.com, ferruh.yigit@intel.com
Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH v2] net/octeontx: set allow experimental API flag in meson
Date: Mon,  5 Feb 2018 22:49:49 +0530	[thread overview]
Message-ID: <20180205171949.7971-1-pbhagavatula@caviumnetworks.com> (raw)
In-Reply-To: <20180205105800.26244-1-pbhagavatula@caviumnetworks.com>

Set allow_experimental_apis to true to allow the use of experimental
API's.

Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
---

 v2 Changes:
 - Use allow_experimental_apis instead of specifying
 '-DALLOW_EXPERIMENTAL_API' through cflags.

 drivers/net/octeontx/meson.build | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/net/octeontx/meson.build b/drivers/net/octeontx/meson.build
index ef789eaa9..0e249eb98 100644
--- a/drivers/net/octeontx/meson.build
+++ b/drivers/net/octeontx/meson.build
@@ -8,6 +8,8 @@ sources = files('octeontx_rxtx.c',
 		'octeontx_ethdev.c'
 		)

+allow_experimental_apis = true
+
 deps += ['mempool_octeontx', 'eventdev']

 includes += include_directories('base')
--
2.14.1

  reply	other threads:[~2018-02-05 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 10:58 [dpdk-dev] [PATCH] net/octeontx: add allow experimental define as flag to meson Pavan Nikhilesh
2018-02-05 17:19 ` Pavan Nikhilesh [this message]
2018-02-05 18:59   ` [dpdk-dev] [PATCH v2] net/octeontx: set allow experimental API flag in meson 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=20180205171949.7971-1-pbhagavatula@caviumnetworks.com \
    --to=pbhagavatula@caviumnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=santosh.shukla@caviumnetworks.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).