From: Thomas Monjalon <thomas@monjalon.net>
To: "J.J. Martzki" <mars14850@gmail.com>
Cc: dev@dpdk.org, stephen@networkplumber.org,
konstantin.ananyev@huawei.com,
Ruifeng Wang <ruifeng.wang@arm.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: Re: [PATCH v5] lib/bpf: Rename bpf function names to avoid potential conflict with libpcap
Date: Mon, 20 Mar 2023 12:50:43 +0100 [thread overview]
Message-ID: <3559438.hdfAi7Kttb@thomas> (raw)
In-Reply-To: <91770103-3420-e248-5727-8ef5df4f4970@yandex.ru>
16/03/2023 01:58, Konstantin Ananyev:
> 14/03/2023 14:20, J.J. 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: J.J. Martzki <mars14850@gmail.com>
>
> Acked-by: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Applied, thanks.
prev parent reply other threads:[~2023-03-20 11:50 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' " 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
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 [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=3559438.hdfAi7Kttb@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--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 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).