From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH dpdk] i40e/ppc64/altivec: Fix compile errors on POWER8
Date: Fri, 21 Apr 2017 13:12:41 +1000 [thread overview]
Message-ID: <60e02a37-fadc-c466-bd32-b1b5245b1a04@ozlabs.ru> (raw)
In-Reply-To: <20170421031010.2389-1-aik@ozlabs.ru>
On 21/04/17 13:10, Alexey Kardashevskiy wrote:
> Fixes: 67f038076657 ("net/i40e: enable per-device packet type mapping")
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
ah, never mind, fixed already.
> ---
> drivers/net/i40e/i40e_rxtx_vec_altivec.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/i40e/i40e_rxtx_vec_altivec.c b/drivers/net/i40e/i40e_rxtx_vec_altivec.c
> index 07de31b01..f4036ea28 100644
> --- a/drivers/net/i40e/i40e_rxtx_vec_altivec.c
> +++ b/drivers/net/i40e/i40e_rxtx_vec_altivec.c
> @@ -208,13 +208,13 @@ desc_to_ptype_v(vector unsigned long descs[4], struct rte_mbuf **rx_pkts,
> ptype1 = vec_sr(ptype1, (vector unsigned long){30, 30});
>
> rx_pkts[0]->packet_type =
> - ptype_tbl[(*(vector unsigned char *)&ptype0)[0])];
> + ptype_tbl[(*(vector unsigned char *)&ptype0)[0]];
> rx_pkts[1]->packet_type =
> - ptype_tbl[(*(vector unsigned char *)&ptype0)[8])];
> + ptype_tbl[(*(vector unsigned char *)&ptype0)[8]];
> rx_pkts[2]->packet_type =
> - ptype_tbl[(*(vector unsigned char *)&ptype1)[0])];
> + ptype_tbl[(*(vector unsigned char *)&ptype1)[0]];
> rx_pkts[3]->packet_type =
> - ptype_tbl[(*(vector unsigned char *)&ptype1)[8])];
> + ptype_tbl[(*(vector unsigned char *)&ptype1)[8]];
> }
>
> /* Notice:
>
--
Alexey
next prev parent reply other threads:[~2017-04-21 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 3:10 Alexey Kardashevskiy
2017-04-21 3:12 ` Alexey Kardashevskiy [this message]
2017-04-21 3:23 ` Zhang, Qi Z
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=60e02a37-fadc-c466-bd32-b1b5245b1a04@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=dev@dpdk.org \
/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).