04/05/2022 22:40, David Christensen:
> On 5/3/22 5:03 AM, Thomas Monjalon wrote:
> > The keyword "vector" may conflict easily.
> > As a rule, it is better to use the alternative keyword "__vector".
> >
> > Signed-off-by: Thomas Monjalon
>
> Reviewed-by: David Christensen
Applied with a longer
On 5/3/22 5:03 AM, Thomas Monjalon wrote:
The keyword "vector" may conflict easily.
As a rule, it is better to use the alternative keyword "__vector".
Signed-off-by: Thomas Monjalon
---
drivers/net/i40e/i40e_rxtx_vec_altivec.c | 214 ++--
drivers/net/mlx5/mlx5_rxtx_vec_altivec.h |
On Tue, May 03, 2022 at 05:44:26PM +0200, Thomas Monjalon wrote:
> 03/05/2022 14:30, Bruce Richardson:
> > On Tue, May 03, 2022 at 02:03:21PM +0200, Thomas Monjalon wrote:
> > > The keyword "vector" may conflict easily.
> > > As a rule, it is better to use the alternative keyword "__vector".
>
> I
03/05/2022 14:30, Bruce Richardson:
> On Tue, May 03, 2022 at 02:03:21PM +0200, Thomas Monjalon wrote:
> > The keyword "vector" may conflict easily.
> > As a rule, it is better to use the alternative keyword "__vector".
I forgot to say that we should #undef vector.
> hi Thomas,
>
> could you per
On Tue, May 03, 2022 at 02:03:21PM +0200, Thomas Monjalon wrote:
> The keyword "vector" may conflict easily.
> As a rule, it is better to use the alternative keyword "__vector".
>
hi Thomas,
could you perhaps clarify a bit more in the log, I'm not aware of it being
a keyword generally. What woul
The keyword "vector" may conflict easily.
As a rule, it is better to use the alternative keyword "__vector".
Signed-off-by: Thomas Monjalon
---
drivers/net/i40e/i40e_rxtx_vec_altivec.c | 214 ++--
drivers/net/mlx5/mlx5_rxtx_vec_altivec.h | 1078 -
.../net/virtio/virtio
6 matches
Mail list logo