Hi,
> -----Original Message-----
> From: David Christensen <d...@linux.vnet.ibm.com>
> Sent: Thursday, April 30, 2020 10:41 PM
> To: Ori Kam <or...@mellanox.com>; Thomas Monjalon
> <tho...@monjalon.net>; Matan Azrad <ma...@mellanox.com>; Shahaf
> Shuler <shah...@mellanox.com>; Slava Ovsiienko
> <viachesl...@mellanox.com>; Beilei Xing <beilei.x...@intel.com>; Qi Zhang
> <qi.z.zh...@intel.com>; Maxime Coquelin
> <maxime.coque...@redhat.com>; Zhihong Wang
> <zhihong.w...@intel.com>; Xiaolong Ye <xiaolong...@intel.com>
> Cc: Raslan Darawsheh <rasl...@mellanox.com>;
> david.march...@redhat.com; dev@dpdk.org; ferruh.yi...@intel.com
> Subject: Re: [PATCH v2] eal/ppc: fix redefine bool type
>
>
>
> On 4/30/20 7:22 AM, Ori Kam wrote:
> > The AltiVec header file breaks boolean type. [1] [2]
> >
> > Currently the workaround was located only in mlx5 device.
> > Adding the trace module caused this issue to appear again, due to
> > order of includes, it keeps overriding the local fix.
> >
> > This patch solves this issue by resetting the bool type, immediately
> > after it is being changed.
> ...
> > Fixes: 725f5dd0bfb5 ("net/mlx5: fix build on PPC64")
> >
> > Signed-off-by: Ori Kam <or...@mellanox.com>
> > Signed-off-by: David Christensen <d...@linux.vnet.ibm.com>
> > ---
> > v2:
> > * Replace alitvec include in all files.
> > * Address ML comments.
> > ---
> Tested-by: David Christensen <d...@linux.vnet.ibm.com>
Tested-by: Raslan Darawsheh <rasl...@mellanox.com>
Kindest regards,
Raslan Darawsheh
