DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce removal of old port count function
Date: Tue, 6 Aug 2019 13:56:23 +0000	[thread overview]
Message-ID: <BYAPR18MB242437857C4E50DC028270AFC8D50@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Tuesday, August 6, 2019 7:02 PM
> To: dev@dpdk.org
> Cc: David Marchand <david.marchand@redhat.com>
> Subject: [dpdk-dev] [PATCH v2] doc: announce removal of old port count
> function
> 
> The function rte_eth_dev_count() was marked as deprecated in DPDK 18.05
> in commit d9a42a69febf ("ethdev: deprecate port count function").
> It is planned to be removed after the next LTS release.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: David Marchand <david.marchand@redhat.com>

Acked-by: Jerin Jacob <jerinj@marvell.com>


> ---
> v2: move notice near other ethdev one
> ---
>  doc/guides/rel_notes/deprecation.rst | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 37b8592b6..3f0fb3ab6 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -51,6 +51,11 @@ Deprecation Notices
>    structure would be made internal (or removed if all dependencies are
> cleared)
>    in future releases.
> 
> +* ethdev: The function ``rte_eth_dev_count`` will be removed in DPDK
> 20.02.
> +  It is replaced by the function ``rte_eth_dev_count_avail``.
> +  If the intent is to iterate over ports, ``RTE_ETH_FOREACH_*`` macros
> +  are better port iterators.
> +
>  * ethdev: the legacy filter API, including
>    ``rte_eth_dev_filter_supported()``, ``rte_eth_dev_filter_ctrl()`` as well
>    as filter types MACVLAN, ETHERTYPE, FLEXIBLE, SYN, NTUPLE, TUNNEL,
> FDIR,
> --
> 2.21.0


             reply	other threads:[~2019-08-06 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 13:56 Jerin Jacob Kollanukkaran [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-03 21:47 [dpdk-dev] [PATCH] " Thomas Monjalon
2019-08-06 13:31 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2019-08-06 13:39   ` Ananyev, Konstantin
2019-08-06 13:45     ` Andrew Rybchenko
2019-08-10 20:35       ` 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=BYAPR18MB242437857C4E50DC028270AFC8D50@BYAPR18MB2424.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@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).