From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbox@nvidia.com>
Subject: Re: [RFC] net/virtio: avoid global variable name conflicts
Date: Mon, 29 Dec 2025 11:07:14 -0800 [thread overview]
Message-ID: <20251229110650.6df093d5@phoenix.local> (raw)
In-Reply-To: <20251222004446.62076-1-stephen@networkplumber.org>
On Sun, 21 Dec 2025 16:44:46 -0800
Stephen Hemminger <stephen@networkplumber.org> wrote:
> If PMD is statically linked, all global variables are visible and
> can clash with application or other drivers and therefore should
> have a consistent prefix.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Recheck-request: iol-intel-Functional
prev parent reply other threads:[~2025-12-29 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 0:44 [RFC] net/virtio: avoid global variable name conflicts Stephen Hemminger
2025-12-29 19:07 ` Stephen Hemminger [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=20251229110650.6df093d5@phoenix.local \
--to=stephen@networkplumber.org \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
/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).