From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-dev] [PATCH] doc: announce malloc virt2phys symbol removal
Date: Fri, 2 Aug 2019 15:29:23 +0200 [thread overview]
Message-ID: <1564752563-11850-1-git-send-email-david.marchand@redhat.com> (raw)
This symbol has been deprecated for quite some time.
Let's drop it in the next release.
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
doc/guides/rel_notes/deprecation.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index b57720c..3c98a5c 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -41,6 +41,9 @@ Deprecation Notices
* eal: The ``rte_cpu_check_supported`` function has been deprecated since
v17.08 and will be removed in DPDK 19.11.
+* eal: The ``rte_malloc_virt2phy`` function has been deprecated and replaced
+ by ``rte_malloc_virt2iova`` since v17.11 and will be removed in DPDK 19.11.
+
* 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.
--
1.8.3.1
next reply other threads:[~2019-08-02 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 13:29 David Marchand [this message]
2019-08-02 16:04 ` Burakov, Anatoly
2019-08-02 16:10 ` Jerin Jacob Kollanukkaran
2019-08-05 14:39 ` Thomas Monjalon
2019-08-05 15:05 ` David Marchand
2019-08-05 15:13 ` Thomas Monjalon
2019-08-12 10:42 ` Kinsella, Ray
2019-08-06 13:50 ` Andrew Rybchenko
2019-08-06 14:00 ` Ananyev, Konstantin
2019-08-08 9:32 ` [dpdk-dev] [PATCH v2] " David Marchand
2019-08-08 15:44 ` 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=1564752563-11850-1-git-send-email-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.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).