From: Thomas Monjalon <thomas@monjalon.net>
To: Martzki <mars14850@gmail.com>
Cc: dev@dpdk.org, stephen@networkplumber.org,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Ruifeng Wang <ruifeng.wang@arm.com>
Subject: Re: [PATCH v3] lib/bpf: Rename bpf function names to avoid potential conflict with libpcap
Date: Sat, 11 Mar 2023 10:18:32 +0100 [thread overview]
Message-ID: <18050202.sWSEgdgrri@thomas> (raw)
In-Reply-To: <20230306154216.41154-1-mars14850@gmail.com>
06/03/2023 16:42, Martzki:
> The library libpcap has their function 'bpf_validate' either so there would
> be a multiple definition issue when linking with librte_bpf.a and libpcap.a
> statically (Same as http://dpdk.org/patch/52631). So just rename the
> function names to avoid such issue.
>
> Signed-off-by: Martzki <mars14850@gmail.com>
Please could you provide you first name and last name?
next prev parent reply other threads:[~2023-03-11 9:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 13:56 [PATCH] lib/bpf: Rename 'bpf_validate' to avoid potential conflict with libpcap Martzki
2023-03-05 17:16 ` Stephen Hemminger
2023-03-05 17:31 ` Stephen Hemminger
2023-03-06 15:32 ` [PATCH v2] lib/bpf: Rename bpf function names " Martzki
2023-03-06 15:42 ` [PATCH v3] " Martzki
2023-03-11 9:18 ` Thomas Monjalon [this message]
2023-03-12 6:20 ` [PATCH v4] " J.J. Martzki
2023-03-12 14:02 ` Konstantin Ananyev
2023-03-13 1:50 ` J.J. Mars
2023-03-13 14:55 ` J.J. Martzki
2023-03-13 15:54 ` Stephen Hemminger
2023-03-13 17:07 ` Konstantin Ananyev
2023-03-13 17:22 ` Stephen Hemminger
2023-03-14 2:21 ` 马尔斯
2023-03-14 14:20 ` [PATCH v5] " J.J. Martzki
2023-03-16 0:58 ` Konstantin Ananyev
2023-03-20 11:50 ` 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=18050202.sWSEgdgrri@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mars14850@gmail.com \
--cc=ruifeng.wang@arm.com \
--cc=stephen@networkplumber.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 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.