DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Christensen <drc@linux.vnet.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Cc: Beilei Xing <beilei.xing@intel.com>,
	Matan Azrad <matan@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Chenbo Xia <chenbo.xia@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH] avoid AltiVec keyword vector
Date: Wed, 4 May 2022 13:40:05 -0700	[thread overview]
Message-ID: <cf080b8b-f327-f91a-e0af-fd8f9e104f6b@linux.vnet.ibm.com> (raw)
In-Reply-To: <20220503120321.2438479-1-thomas@monjalon.net>

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 <thomas@monjalon.net>
> ---
>   drivers/net/i40e/i40e_rxtx_vec_altivec.c      |  214 ++--
>   drivers/net/mlx5/mlx5_rxtx_vec_altivec.h      | 1078 ++++++++---------
>   .../net/virtio/virtio_rxtx_simple_altivec.c   |   70 +-
>   examples/l3fwd/l3fwd_lpm_altivec.h            |   14 +-
>   lib/eal/ppc/include/rte_vect.h                |    2 +-
>   lib/lpm/rte_lpm_altivec.h                     |    6 +-
>   6 files changed, 692 insertions(+), 692 deletions(-)

Reviewed-by: David Christensen <drc@linux.vnet.ibm.com>

  parent reply	other threads:[~2022-05-04 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 12:03 Thomas Monjalon
2022-05-03 12:30 ` Bruce Richardson
2022-05-03 15:44   ` Thomas Monjalon
2022-05-04  6:30     ` Tyler Retzlaff
2022-05-04 20:40 ` David Christensen [this message]
2022-05-25  8:18   ` Thomas Monjalon

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=cf080b8b-f327-f91a-e0af-fd8f9e104f6b@linux.vnet.ibm.com \
    --to=drc@linux.vnet.ibm.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \
    --cc=vladimir.medvedkin@intel.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).