DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Trahe, Fiona" <fiona.trahe@intel.com>
Cc: David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>,
	Jerin Jacob <jerinjacobk@gmail.com>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v5] build: disable experimental API check internally
Date: Fri, 17 Apr 2020 15:54:12 +0200	[thread overview]
Message-ID: <3060691.oqx4rD5t72@thomas> (raw)
In-Reply-To: <SN6PR11MB28801C35936663AEA4F6E774E4D90@SN6PR11MB2880.namprd11.prod.outlook.com>

17/04/2020 15:44, Trahe, Fiona:
> From: David Marchand <david.marchand@redhat.com>
> > On Fri, Apr 17, 2020 at 12:21 PM Trahe, Fiona <fiona.trahe@intel.com> wrote:
> > > I see this is already applied.
> > >
> > > However,
> > > rte_cryptodev_queue_pair_setup() calls
> > > rte_cryptodev_sym_get_existing_header_session_size()
> > > The former is a stable API, the latter is experimental.
> > > So I expect the build to break when ALLOW_EXPERIMENTAL_API is disabled.
> [Fiona] Thanks for confirming where the flag is.
> But I think you've missed my point.
> What about this problem?
> How was this tested with the flag disabled?

We are not supposed to disable the flag internally.
The examples are not affected by the global enablement,
so you can test non-experimental build with examples.




  reply	other threads:[~2020-04-17 13:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 18:32 [dpdk-dev] [PATCH v2 1/2] build: meson make experimental tag as global Jerin Jacob
2020-04-02 18:32 ` [dpdk-dev] [PATCH v2 2/2] build: makefile " Jerin Jacob
2020-04-03  7:23 ` [dpdk-dev] [PATCH v2 1/2] build: meson " David Marchand
2020-04-03  7:45   ` David Marchand
2020-04-03  8:05     ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2020-04-03  8:18       ` David Marchand
2020-04-03  9:10         ` Bruce Richardson
2020-04-03  9:14           ` David Marchand
2020-04-03  9:35             ` Bruce Richardson
2020-04-03 10:56       ` Thomas Monjalon
2020-04-03 11:02         ` Pavan Nikhilesh Bhagavatula
2020-04-03 10:20 ` [dpdk-dev] " Hemant Agrawal (OSS)
2020-04-03 14:19 ` [dpdk-dev] [PATCH v3] build: enable allow experimental API flag globally pbhagavatula
2020-04-06 20:16   ` David Marchand
2020-04-10  9:03   ` [dpdk-dev] [PATCH v4] build: enable allow experimental API flag pbhagavatula
2020-04-10 12:12     ` David Marchand
2020-04-10 15:48       ` David Marchand
2020-04-13 14:55 ` [dpdk-dev] [PATCH v5] build: disable experimental API check internally David Marchand
2020-04-14 14:23   ` David Marchand
2020-04-17 10:21     ` Trahe, Fiona
2020-04-17 13:23       ` David Marchand
2020-04-17 13:44         ` Trahe, Fiona
2020-04-17 13:54           ` Thomas Monjalon [this message]
2020-04-17 13:56           ` David Marchand
2020-04-17 15:05             ` Trahe, Fiona
2020-04-17 15:52               ` Trahe, Fiona
2020-04-18 19:43                 ` Chautru, Nicolas
2020-04-19  7:35                   ` David Marchand
2020-04-19 16:17                     ` Chautru, Nicolas

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=3060691.oqx4rD5t72@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinjacobk@gmail.com \
    --cc=pbhagavatula@marvell.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).