From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce removal of old port count function
Date: Tue, 04 Jun 2019 09:17:16 +0200 [thread overview]
Message-ID: <1642772.YoMAR6jVNy@xps> (raw)
In-Reply-To: <CAJFAV8yYuGPiXka5c1CDgDBQ2wbtG_NmsPTFv1Eg2XKGMDmxfA@mail.gmail.com>
04/06/2019 09:12, David Marchand:
> On Mon, Jun 3, 2019 at 11:48 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -37,6 +37,11 @@ Deprecation Notices
> >
> > + ``rte_eal_devargs_type_count``
> >
> > +* 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.
> > +
> > * vfio: removal of ``rte_vfio_dma_map`` and ``rte_vfio_dma_unmap`` APIs
> > which
> > have been replaced with ``rte_dev_dma_map`` and ``rte_dev_dma_unmap``
> > functions. The due date for the removal targets DPDK 20.02.
>
> Out of curiosity (ok, not entirely, since I need to write some notices).
> Is there a rule for the order in which those entries are written?
Yes the order should be the same as for the features in the release notes.
> I can see a notice about ethdev later in the file.
Indeed, ethdev is supposed to be after EAL,
it is my mistake.
> Acked-by: David Marchand <david.marchand@redhat.com>
next prev parent reply other threads:[~2019-06-04 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 21:47 Thomas Monjalon
2019-06-04 7:12 ` David Marchand
2019-06-04 7:17 ` Thomas Monjalon [this message]
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=1642772.YoMAR6jVNy@xps \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).