From: fengchengwen <fengchengwen@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <thomas@monjalon.net>, <david.marchand@redhat.com>, <dev@dpdk.org>
Subject: Re: [PATCH] dpdk: support quick jump to API definition
Date: Fri, 29 Aug 2025 09:37:05 +0800 [thread overview]
Message-ID: <6f88d1bd-234d-494d-87e1-b571ea522d44@huawei.com> (raw)
In-Reply-To: <83849498-c22a-44d3-b0ab-fb2887bbf536@huawei.com>
add more info
On 8/29/2025 9:31 AM, fengchengwen wrote:
> On 8/28/2025 10:47 PM, Stephen Hemminger wrote:
>> On Thu, 28 Aug 2025 10:46:31 +0800
>> Chengwen Feng <fengchengwen@huawei.com> wrote:
>>
>>> Currently, the RTE_EXPORT_INTERNAL_SYMBOL, RTE_EXPORT_SYMBOL and
>>> RTE_EXPORT_EXPERIMENTAL_SYMBOL are placed at the beginning of APIs,
>>> but don't end with a semicolon. As a result, some IDEs cannot identify
>>> the APIs and cannot quickly jump to the definition.
>>>
>>> A semicolon is added to the end of above RTE_EXPORT_XXX_SYMBOL in this
>>> commit.
>>>
>>> And also change the gen-version-map.py to ensure it only identifies
>>> RTE_EXPORT_XXX_SYMBOL that end with a semicolon.
>>>
>>> Signed
>>
>> Semicolon after macro will cause scripts like checkpatch to complain?
>
> No
>
> This commit trigger a checkpatch error because the following function add two semicolon.
>
> RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_node_mbuf_dynfield_register, 25.07);;
>
>
> Because the RTE_EXPORT_XXX_SYMBOL(XXX) macro do nothing, and this macro are placed out side
> of function, it will left one semicolon after pre-process. This is not strictly comply with
> C stand syntax.
>
> In the V2 I will adopt following:
> 1\ #define RTE_EXPORT_XXX_SYMBOL(XXX) extern int __dummy_unused__ , this definition is comply
> with C stand syntax.
> 2\ keep the gen-version-map.py un-touch, because some commit are in-process different branch.
Two step:
1\ keep the RTE_EXPORT_XXX_SYMBOL definition and gen-version-map.py un-touched, and fix all CI error.
2\ #define RTE_EXPORT_XXX_SYMBOL(XXX) extern int __dummy_unused__ and modify remains or new definitions.
>
> Thanks.
next prev parent reply other threads:[~2025-08-29 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 2:46 Chengwen Feng
2025-08-28 14:47 ` Stephen Hemminger
2025-08-29 1:31 ` fengchengwen
2025-08-29 1:37 ` fengchengwen [this message]
2025-08-28 2:59 Chengwen Feng
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=6f88d1bd-234d-494d-87e1-b571ea522d44@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).