DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
	 Bruce Richardson <bruce.richardson@intel.com>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] rawdev: fix to remove EXPERIMENTAL from comment
Date: Tue, 7 Jul 2020 11:13:25 +0200	[thread overview]
Message-ID: <CAJFAV8xNjQQreNQj5b-QSTGimC4cSu5_xYVdcObnkouKhAdYHQ@mail.gmail.com> (raw)
In-Reply-To: <20200707085407.12555-1-hemant.agrawal@nxp.com>

On Tue, Jul 7, 2020 at 10:58 AM Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
>
> The experimental tags were removed, but the comment
> is still having API classification as EXPERIMENTAL
>
> Fixes: 931cc531aad2 ("rawdev: remove experimental tag")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
>  MAINTAINERS                        | 2 +-
>  lib/librte_rawdev/rte_rawdev.h     | 3 ---
>  lib/librte_rawdev/rte_rawdev_pmd.h | 3 ---
>  3 files changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 27fcd6d648..6ba02d73aa 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -490,7 +490,7 @@ F: lib/librte_eventdev/*crypto_adapter*
>  F: app/test/test_event_crypto_adapter.c
>  F: doc/guides/prog_guide/event_crypto_adapter.rst
>
> -Raw device API - EXPERIMENTAL
> +Raw device API
>  M: Nipun Gupta <nipun.gupta@nxp.com>
>  M: Hemant Agrawal <hemant.agrawal@nxp.com>
>  F: lib/librte_rawdev/
> diff --git a/lib/librte_rawdev/rte_rawdev.h b/lib/librte_rawdev/rte_rawdev.h
> index ed011ca228..7a1f3213e9 100644
> --- a/lib/librte_rawdev/rte_rawdev.h
> +++ b/lib/librte_rawdev/rte_rawdev.h
> @@ -12,9 +12,6 @@
>   *
>   * This API allow applications to configure and use generic devices having
>   * no specific type already available in DPDK.
> - *
> - * @warning
> - * @b EXPERIMENTAL: this API may change without prior notice
>   */
>
>  #ifdef __cplusplus
> diff --git a/lib/librte_rawdev/rte_rawdev_pmd.h b/lib/librte_rawdev/rte_rawdev_pmd.h
> index cb3555ab50..4395a2182d 100644
> --- a/lib/librte_rawdev/rte_rawdev_pmd.h
> +++ b/lib/librte_rawdev/rte_rawdev_pmd.h
> @@ -11,9 +11,6 @@
>   * @note
>   * Driver facing APIs for a raw device. These are not to be called directly by
>   * any application.
> - *
> - * @warning
> - * @b EXPERIMENTAL: this API may change without prior notice
>   */
>
>  #ifdef __cplusplus
> --
> 2.17.1
>

Acked-by: David Marchand <david.marchand@redhat.com>


-- 
David Marchand


  parent reply	other threads:[~2020-07-07  9:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07  6:53 [dpdk-dev] [PATCH] " Hemant Agrawal
2020-07-07  7:22 ` Thomas Monjalon
2020-07-07  8:54 ` [dpdk-dev] [PATCH v2] " Hemant Agrawal
2020-07-07  9:02   ` Thomas Monjalon
2020-07-07  9:08     ` Ferruh Yigit
2020-07-07  9:13   ` David Marchand [this message]
2020-07-07 10:56     ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=CAJFAV8xNjQQreNQj5b-QSTGimC4cSu5_xYVdcObnkouKhAdYHQ@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=stable@dpdk.org \
    --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).