From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org, techboard@dpdk.org
Cc: Ray Kinsella <mdr@ashroe.eu>
Subject: [PATCH] doc: announce marking bus object as internal
Date: Thu, 30 Jun 2022 11:41:53 +0200 [thread overview]
Message-ID: <20220630094153.2066208-1-david.marchand@redhat.com> (raw)
rte_bus is unnecessarily exposed in the public API/ABI.
Besides, we had cases where extending rte_bus was necessary.
Announce that rte_bus will be made opaque in the public API and mark
associated API as internal.
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
A RFC series of the intended changes is available at:
https://patches.dpdk.org/project/dpdk/list/?series=23811&state=%2A&archive=both
---
doc/guides/rel_notes/deprecation.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 64d649777a..a9fd6676be 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -32,6 +32,12 @@ Deprecation Notices
``__atomic_thread_fence`` must be used for patches that need to be merged in
20.08 onwards. This change will not introduce any performance degradation.
+* bus: The ``rte_bus`` object will be made opaque in DPDK 22.11.
+ The goal is to remove it from the public ABI and make this object extendable.
+ As a side effect, registering a bus will be marked as an internal API:
+ external users may still register their bus using a new driver header (see
+ ``enable_driver_sdk`` meson option).
+
* mempool: Helper macro ``MEMPOOL_HEADER_SIZE()`` is deprecated and will
be removed in DPDK 22.11. The replacement macro
``RTE_MEMPOOL_HEADER_SIZE()`` is internal only.
--
2.36.1
next reply other threads:[~2022-06-30 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 9:41 David Marchand [this message]
2022-06-30 9:54 ` Bruce Richardson
2022-06-30 14:36 ` Thomas Monjalon
2022-07-04 14:29 ` Kevin Laatz
2022-07-05 4:43 ` Hemant Agrawal
2022-07-05 6:59 ` Andrew Rybchenko
2022-07-15 16:16 ` 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=20220630094153.2066208-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
--cc=techboard@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).