ment we won't need
to update it in the future.
> -Original Message-
> From: Akhil Goyal [mailto:akhil.go...@nxp.com]
> Sent: Thursday, October 3, 2019 10:30 AM
> To: Ananyev, Konstantin ; Smoczynski,
> MarcinX ; Iremonger, Bernard
>
> Cc: dev@dpdk.org
> Su
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Sunday, September 29, 2019 7:04 PM
> To: Smoczynski, MarcinX ;
> ano...@marvell.com; akhil.go...@nxp.com
> Cc: dev@dpdk.org
> Subject: RE: [PATCH v5 2/4] examples/ipsec-secgw: add fallback session
>
Joseph, is this patchset ok with you after changes? I've changed second
patch description and sample application documentation regarding this
feature.
> -Original Message-
> From: Smoczynski, MarcinX
> Sent: Monday, September 23, 2019 1:44 PM
> To: ano...@marvell.com; ak
> -Original Message-
> From: Gavin Hu (Arm Technology China) [mailto:gavin...@arm.com]
> Sent: Thursday, September 5, 2019 7:44 AM
> To: Smoczynski, MarcinX ; Ananyev,
> Konstantin ; Wiles, Keith
> ; adrien.mazarg...@6wind.com
> Cc: dev@dpdk.org; sta...@dpdk
Hi Akhil,
I've double checked and there is no problem with linking application against
shared libraries, because inline functions are being inlined during compilation
and before linking is done. To be more specific: there is not such symbol as
rte_ipv6_get_next_ext in ipsec-secgw.o (which uses t
Is my action required to merge patches? e.g. do I need to send rebased patches
(however there are no conflicts at the moment)?
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Wednesday, June 5, 2019 12:16 PM
> To: Smoczynski, MarcinX ; Richardson,
> Bruce ; tho.
> -Original Message-
> From: Richardson, Bruce
> Sent: Tuesday, May 14, 2019 2:20 PM
> To: Smoczynski, MarcinX
> Cc: tho...@monjalon.net; dev@dpdk.org; Ananyev, Konstantin
> ; adrien.mazarg...@6wind.com
> Subject: Re: [PATCH] build: enable BSD features visibilit
> > Hey Konstantin,
> >
> > On Mon, May 13, 2019 at 10:49:00AM +, Ananyev, Konstantin wrote:
> > > Hi Adrien,
> > >
> > > >
> > > > On Mon, May 13, 2019 at 09:51:24AM +, Smoczynski, MarcinX
> wrote:
> > > > &g
10/05/2019 20:17, Thomas Monjalon:
> 10/05/2019 19:14, Smoczynski, MarcinX:
> > To summarize we have different visibility sets for Linux and BSD
> > when using XOPEN_SOURCE or POSIX_C_SOURCE explicitly. To overcome
> > this situation we can either remove problematic XOPE
Hi.
One of my patches submitted this week is breaking build on BSD systems. I dug
deeper and found out that it's because I'm using IPPROTO_* macros from
in a header (rte_ip.h) which is included in the driver which uses
_XOPEN_SOURCE definition in its Makefile/meson.build.
On Linux and glibc this
10 matches
Mail list logo
