DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Joyce Kong <joyce.kong@arm.com>,
	Ruifeng Wang <ruifeng.wang@arm.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "nd@arm.com" <nd@arm.com>
Subject: RE: [PATCH v1] net/i40e: fix build issue with 16B descriptor on Arm
Date: Tue, 8 Mar 2022 23:24:50 +0000	[thread overview]
Message-ID: <b494d9df8463467fa3c74184872070b0@intel.com> (raw)
In-Reply-To: <20220304073517.2000817-1-joyce.kong@arm.com>



> -----Original Message-----
> From: Joyce Kong <joyce.kong@arm.com>
> Sent: Friday, March 4, 2022 3:35 PM
> To: Ruifeng Wang <ruifeng.wang@arm.com>; Xing, Beilei
> <beilei.xing@intel.com>; Joyce Kong <joyce.kong@arm.com>
> Cc: dev@dpdk.org; nd@arm.com
> Subject: [PATCH v1] net/i40e: fix build issue with 16B descriptor on Arm
> 
> For NEON vector path, there is an issue when building with 16B descriptor:
> incompatible types when assigning to type ‘uint64x2_t’
> from type ‘uint32x4_t’
> 180 |  descs[3] = vbslq_u32(v_desc3_mask, v_zeros,
> 			vreinterpretq_u32_u64(descs[3]));
>     |             ^~~~~~~~~
> 
> The fix is to add interpretation between type 'uint64x2_t'
> and type 'uint32x4_t'.
> 
> Fixes: dba9e3bcd9bb ("net/i40e: add flow mark capability to NEON Rx")
> 
> Signed-off-by: Joyce Kong <joyce.kong@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>

Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2022-03-08 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04  7:35 Joyce Kong
2022-03-08 23:24 ` Zhang, Qi Z [this message]

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=b494d9df8463467fa3c74184872070b0@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=joyce.kong@arm.com \
    --cc=nd@arm.com \
    --cc=ruifeng.wang@arm.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).