From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
Gavin Hu <gavin.hu@arm.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] lib/librte_table: fix arm64 hash function selection
Date: Mon, 8 Apr 2019 13:37:31 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E8727D3@IRSMSX108.ger.corp.intel.com> (raw)
Message-ID: <20190408133731.olmPkDvGDyWNAroKl-ptcHAsRUmbQp1C13H5OmfznFY@z> (raw)
In-Reply-To: <20190406132852.14862-1-jerinj@marvell.com>
> -----Original Message-----
> From: Jerin Jacob Kollanukkaran [mailto:jerinj@marvell.com]
> Sent: Saturday, April 6, 2019 2:30 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org; thomas@monjalon.net; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>; Gavin Hu <gavin.hu@arm.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] lib/librte_table: fix arm64 hash function
> selection
>
> From: Jerin Jacob <jerinj@marvell.com>
>
> Use CRC32 instruction only when it is available to avoid
> the build issue like below.
>
> {standard input}:16: Error:
> selected processor does not support `crc32cx w3,w3,x0'
>
> Fixes: ea7be0a0386e ("lib/librte_table: add hash function headers")
> Cc: Gavin Hu <gavin.hu@arm.com>
> Cc: stable@dpdk.org
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
> lib/librte_table/rte_table_hash_func.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2019-04-08 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 13:29 Jerin Jacob Kollanukkaran
2019-04-06 13:29 ` Jerin Jacob Kollanukkaran
2019-04-08 13:37 ` Dumitrescu, Cristian [this message]
2019-04-08 13:37 ` Dumitrescu, Cristian
2019-04-10 20:05 ` Thomas Monjalon
2019-04-10 20:05 ` 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=3EB4FA525960D640B5BDFFD6A3D891268E8727D3@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=jerinj@marvell.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).