From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Vivian Kong <vivkong@ca.ibm.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Function name collision on bpf_validate
Date: Mon, 8 Apr 2019 15:11:31 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772580148A94616@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <OF56B51D50.79E62A14-ON852583D6.004B92AD-852583D6.004C1A3E@notes.na.collabserv.com>
Hi Vivian,
>
>
>
> Hi,
>
> Has anyone run into this issue with bpf_validate? We have an application
> that links to both DPDK and libpcap and both define bpf_validate.
Didn't hit such issue so far.
Could you provide some basic way to reproduce it?
Thanks
Konstantin
> I
> couldn't find other complaints on this so I'm wondering what would be the
> best way to handle this?
>
> Thanks and I appreciate for your input.
>
> Regards,
>
> Vivian Kong
> Linux on IBM Z Open Source Ecosystem
> IBM Canada Toronto Lab
next prev parent reply other threads:[~2019-04-08 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 13:51 Vivian Kong
2019-04-08 13:51 ` Vivian Kong
2019-04-08 15:11 ` Ananyev, Konstantin [this message]
2019-04-08 15:11 ` Ananyev, Konstantin
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=2601191342CEEE43887BDE71AB9772580148A94616@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=vivkong@ca.ibm.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).