From: Stephen Hemminger <stephen@networkplumber.org>
To: Chengwen Feng <fengchengwen@huawei.com>
Cc: <thomas@monjalon.net>, <david.marchand@redhat.com>, <dev@dpdk.org>
Subject: Re: [PATCH v3 2/5] lib: add semicolon when export experimental symbol
Date: Fri, 5 Sep 2025 21:14:52 -0700 [thread overview]
Message-ID: <20250905211452.13ef8796@hermes.local> (raw)
In-Reply-To: <20250901012149.47887-3-fengchengwen@huawei.com>
On Mon, 1 Sep 2025 09:21:46 +0800
Chengwen Feng <fengchengwen@huawei.com> wrote:
> Currently, the RTE_EXPORT_EXPERIMENTAL_SYMBOL was placed at the
> beginning of APIs, but doesn'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_EXPERIMENTAL_SYMBOL
> in this commit.
>
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> ---
This seems like a big change just to workaround some mis-feature of an IDE
which few users use.
next prev parent reply other threads:[~2025-09-06 4:15 UTC|newest]
Thread overview: 28+ 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 ` [PATCH v2 3/3] doc: update ABI versioning guide Chengwen Feng
2025-09-01 1:21 ` [PATCH v3 0/5] add semicolon when export any symbol Chengwen Feng
2025-09-01 1:21 ` [PATCH v3 1/5] lib: add semicolon when export symbol Chengwen Feng
2025-09-01 1:21 ` [PATCH v3 2/5] lib: add semicolon when export experimental symbol Chengwen Feng
2025-09-06 4:14 ` Stephen Hemminger [this message]
2025-09-01 1:21 ` [PATCH v3 3/5] lib: add semicolon when export internal symbol Chengwen Feng
2025-09-01 1:21 ` [PATCH v3 4/5] drivers: add semicolon when export any symbol Chengwen Feng
2025-09-01 1:21 ` [PATCH v3 5/5] doc: update ABI versioning guide Chengwen Feng
2025-09-01 10:46 ` [PATCH v4 0/5] add semicolon when export any symbol Chengwen Feng
2025-09-01 10:46 ` [PATCH v4 1/5] lib: add semicolon when export symbol Chengwen Feng
2025-09-01 10:46 ` [PATCH v4 2/5] lib: add semicolon when export experimental symbol Chengwen Feng
2025-09-01 10:46 ` [PATCH v4 3/5] lib: add semicolon when export internal symbol Chengwen Feng
2025-09-01 10:46 ` [PATCH v4 4/5] drivers: add semicolon when export any symbol Chengwen Feng
2025-09-01 10:46 ` [PATCH v4 5/5] doc: update ABI versioning guide Chengwen Feng
2025-09-03 2:05 ` [PATCH v5 0/5] add semicolon when export any symbol Chengwen Feng
2025-09-03 2:05 ` [PATCH v5 1/5] lib: add semicolon when export symbol Chengwen Feng
2025-09-03 2:05 ` [PATCH v5 2/5] lib: add semicolon when export experimental symbol Chengwen Feng
2025-09-03 2:05 ` [PATCH v5 3/5] lib: add semicolon when export internal symbol Chengwen Feng
2025-09-03 2:05 ` [PATCH v5 4/5] drivers: add semicolon when export any symbol Chengwen Feng
2025-09-03 2:05 ` [PATCH v5 5/5] doc: update ABI versioning guide Chengwen Feng
2025-09-03 7:04 ` [PATCH v5 0/5] add semicolon when export any symbol David Marchand
2025-09-04 0:24 ` fengchengwen
2025-09-08 7:54 ` David Marchand
2025-09-08 12:43 ` fengchengwen
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=20250905211452.13ef8796@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.