All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Haiyue Wang <haiyue.wang@intel.com>, <dev@dpdk.org>
Cc: <mdr@ashroe.eu>, <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v1 1/3] net/ixgbe: promote some API to stable
Date: Wed, 1 Sep 2021 10:02:07 +0100	[thread overview]
Message-ID: <c31cab46-7cb8-f68f-5733-67cf90427418@intel.com> (raw)
In-Reply-To: <20210901050707.570163-2-haiyue.wang@intel.com>

On 9/1/2021 6:07 AM, Haiyue Wang wrote:
> The DPDK Symbol Bot reports:
> Please note the symbols listed below have expired. In line with the
> DPDK ABI policy, they should be scheduled for removal, in the next
> DPDK release.
> 
> Symbol
> rte_pmd_ixgbe_mdio_lock
> rte_pmd_ixgbe_mdio_unlock
> rte_pmd_ixgbe_mdio_unlocked_read
> rte_pmd_ixgbe_mdio_unlocked_write
> rte_pmd_ixgbe_upd_fctrl_sbp

I wonder if we should keep PMD specific APIs as experimental (Not talking about
mbuf 'dynfield' / 'dynflag' APIs, we can promote them).

If an application is using PMD specific API, not sure if it will concern about
PMD specific APIs.
And keeping PMD specific APIs lets us remove them as soon as we can, also adds
additional discourage for users to use them.

> 
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>


<...>



  reply	other threads:[~2021-09-01  9:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  5:07 [dpdk-dev] [PATCH v1 0/3] Promote some API to stable Haiyue Wang
2021-09-01  5:07 ` [dpdk-dev] [PATCH v1 1/3] net/ixgbe: promote " Haiyue Wang
2021-09-01  9:02   ` Ferruh Yigit [this message]
2021-09-01 11:13     ` Wang, Haiyue
2021-09-01 13:55       ` Kinsella, Ray
2021-09-01  5:07 ` [dpdk-dev] [PATCH v1 2/3] net/ice: " Haiyue Wang
2021-09-01  5:07 ` [dpdk-dev] [PATCH v1 3/3] ethdev: promote burst mode " Haiyue Wang
2021-09-01  9:07   ` Ferruh Yigit
2021-09-01 13:49     ` Kinsella, Ray
2021-09-06  5:56 ` [dpdk-dev] [PATCH v2] " Haiyue Wang
2021-09-06  6:36   ` Andrew Rybchenko
2021-09-15  8:46     ` 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=c31cab46-7cb8-f68f-5733-67cf90427418@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=mdr@ashroe.eu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.