From: David Marchand <david.marchand@redhat.com>
To: Nipun Gupta <nipun.gupta@nxp.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>,
Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [PATCH 2/4] bus/fslmc: remove experimental tag from API
Date: Thu, 9 Sep 2021 10:01:53 +0200 [thread overview]
Message-ID: <CAJFAV8xcaTxgKF9NCM6SoEev+pFeG7qhq0=Vs-MwQjdHE23Uqw@mail.gmail.com> (raw)
In-Reply-To: <DB9PR04MB8429D56C9C5A1B0B7340F4DFE6D59@DB9PR04MB8429.eurprd04.prod.outlook.com>
On Thu, Sep 9, 2021 at 9:54 AM Nipun Gupta <nipun.gupta@nxp.com> wrote:
> > > This API was introduced in 19.08, therefore removing
> > > experimental tag to promote them to stable state.
> >
> > The only user is an in-tree driver.
> > Do we need to export this symbol to applications?
>
> Yes, we intend to export this PMD API to applications.
Thanks for confirming.
--
David Marchand
next prev parent reply other threads:[~2021-09-09 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 7:17 [dpdk-dev] [PATCH 1/4] bus/dpaa: remove experimental tag and move to internal Nipun Gupta
2021-09-03 7:17 ` [dpdk-dev] [PATCH 2/4] bus/fslmc: remove experimental tag from API Nipun Gupta
2021-09-09 7:11 ` Hemant Agrawal
2021-09-09 7:50 ` David Marchand
2021-09-09 7:54 ` Nipun Gupta
2021-09-09 8:01 ` David Marchand [this message]
2021-09-24 16:57 ` Thomas Monjalon
2021-09-03 7:17 ` [dpdk-dev] [PATCH 3/4] bus/fslmc: remove experimental and move to internal Nipun Gupta
2021-09-09 7:11 ` Hemant Agrawal
2021-09-03 7:17 ` [dpdk-dev] [PATCH 4/4] net/dpaa2: remove experimental tag from API Nipun Gupta
2021-09-09 7:12 ` Hemant Agrawal
2021-09-09 7:10 ` [dpdk-dev] [PATCH 1/4] bus/dpaa: remove experimental tag and move to internal Hemant Agrawal
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='CAJFAV8xcaTxgKF9NCM6SoEev+pFeG7qhq0=Vs-MwQjdHE23Uqw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=mdr@ashroe.eu \
--cc=nipun.gupta@nxp.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=thomas@monjalon.net \
/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).