DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Nipun Gupta <nipun.gupta@nxp.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH 2/4] bus/fslmc: remove experimental tag from API
Date: Thu, 9 Sep 2021 07:11:00 +0000	[thread overview]
Message-ID: <DU2PR04MB8630904E43B5D2437367439189D59@DU2PR04MB8630.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210903071714.16798-2-nipun.gupta@nxp.com>

Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

> -----Original Message-----
> From: Nipun Gupta <nipun.gupta@nxp.com>
> Sent: Friday, September 3, 2021 12:47 PM
> To: thomas@monjalon.net
> Cc: dev@dpdk.org; Hemant Agrawal <hemant.agrawal@nxp.com>; Sachin
> Saxena (OSS) <sachin.saxena@oss.nxp.com>; david.marchand@redhat.com;
> Nipun Gupta <nipun.gupta@nxp.com>
> Subject: [PATCH 2/4] bus/fslmc: remove experimental tag from API
> Importance: High
> 
> This API was introduced in 19.08, therefore removing experimental tag to
> promote them to stable state.
> 
> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> ---
>  drivers/bus/fslmc/fslmc_vfio.h | 1 -
>  drivers/bus/fslmc/version.map  | 4 +++-
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/bus/fslmc/fslmc_vfio.h b/drivers/bus/fslmc/fslmc_vfio.h
> index bc7c6f62d7..133606a9fd 100644
> --- a/drivers/bus/fslmc/fslmc_vfio.h
> +++ b/drivers/bus/fslmc/fslmc_vfio.h
> @@ -58,7 +58,6 @@ int fslmc_vfio_process_group(void);  char
> *fslmc_get_container(void);  int fslmc_get_container_group(int *gropuid);
> int rte_fslmc_vfio_dmamap(void); -__rte_experimental  int
> rte_fslmc_vfio_mem_dmamap(uint64_t vaddr, uint64_t iova, uint64_t size);
> 
>  #endif /* _FSLMC_VFIO_H_ */
> diff --git a/drivers/bus/fslmc/version.map b/drivers/bus/fslmc/version.map
> index f44c1a7988..4e53ea048d 100644
> --- a/drivers/bus/fslmc/version.map
> +++ b/drivers/bus/fslmc/version.map
> @@ -1,7 +1,9 @@
> -EXPERIMENTAL {
> +DPDK_22 {
>  	global:
> 
>  	rte_fslmc_vfio_mem_dmamap;
> +
> +	local: *;
>  };
> 
>  INTERNAL {
> --
> 2.17.1


  reply	other threads:[~2021-09-09  7:11 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 [this message]
2021-09-09  7:50   ` David Marchand
2021-09-09  7:54     ` Nipun Gupta
2021-09-09  8:01       ` David Marchand
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=DU2PR04MB8630904E43B5D2437367439189D59@DU2PR04MB8630.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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).