From: Chengwen Feng <fengchengwen@huawei.com>
To: <thomas@monjalon.net>, <david.marchand@redhat.com>,
<stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: [PATCH v2 3/3] doc: update ABI versioning guide
Date: Fri, 29 Aug 2025 10:34:03 +0800 [thread overview]
Message-ID: <20250829023403.4895-4-fengchengwen@huawei.com> (raw)
In-Reply-To: <20250829023403.4895-1-fengchengwen@huawei.com>
Add a semicolon after RTE_EXPORT_INTERNAL_SYMBOL, RTE_EXPORT_SYMBOL and
RTE_EXPORT_EXPERIMENTAL_SYMBOL in the guide.
Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
---
doc/guides/contributing/abi_versioning.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/guides/contributing/abi_versioning.rst b/doc/guides/contributing/abi_versioning.rst
index 2fa2b15edc..0c1135becc 100644
--- a/doc/guides/contributing/abi_versioning.rst
+++ b/doc/guides/contributing/abi_versioning.rst
@@ -168,7 +168,7 @@ Assume we have a function as follows
* Create an acl context object for apps to
* manipulate
*/
- RTE_EXPORT_SYMBOL(rte_acl_create)
+ RTE_EXPORT_SYMBOL(rte_acl_create);
int
rte_acl_create(struct rte_acl_param *param)
{
@@ -187,7 +187,7 @@ private, is safe), but it also requires modifying the code as follows
* Create an acl context object for apps to
* manipulate
*/
- RTE_EXPORT_SYMBOL(rte_acl_create)
+ RTE_EXPORT_SYMBOL(rte_acl_create);
int
rte_acl_create(struct rte_acl_param *param, int debug)
{
@@ -213,7 +213,7 @@ the function return type, the function name and its arguments.
.. code-block:: c
- -RTE_EXPORT_SYMBOL(rte_acl_create)
+ -RTE_EXPORT_SYMBOL(rte_acl_create);
-int
-rte_acl_create(struct rte_acl_param *param)
+RTE_VERSION_SYMBOL(21, int, rte_acl_create, (struct rte_acl_param *param))
@@ -303,7 +303,7 @@ Assume we have an experimental function ``rte_acl_create`` as follows:
* Create an acl context object for apps to
* manipulate
*/
- RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_acl_create)
+ RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_acl_create);
__rte_experimental
int
rte_acl_create(struct rte_acl_param *param)
@@ -320,7 +320,7 @@ When we promote the symbol to the stable ABI, we simply strip the
* Create an acl context object for apps to
* manipulate
*/
- RTE_EXPORT_SYMBOL(rte_acl_create)
+ RTE_EXPORT_SYMBOL(rte_acl_create);
int
rte_acl_create(struct rte_acl_param *param)
{
--
2.17.1
prev parent reply other threads:[~2025-08-29 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 2:59 [PATCH] dpdk: support quick jump to API definition Chengwen Feng
2025-08-29 2:34 ` [PATCH v2 0/3] " Chengwen Feng
2025-08-29 2:34 ` [PATCH v2 1/3] lib: " Chengwen Feng
2025-08-29 2:34 ` [PATCH v2 2/3] drivers: " Chengwen Feng
2025-08-29 2:34 ` Chengwen Feng [this message]
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=20250829023403.4895-4-fengchengwen@huawei.com \
--to=fengchengwen@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).