DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@oss.nvidia.com>
To: Akhil Goyal <gakhil@marvell.com>,
	NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	Tejasree Kondoj <ktejasree@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [pull-request] next-crypto 21.08 rc1
Date: Thu, 8 Jul 2021 17:13:42 +0000	[thread overview]
Message-ID: <DM4PR12MB51678615814B51DAE8D0944CDA199@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210707193058.1035564-1-gakhil@marvell.com>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Akhil Goyal
> Sent: Wednesday, July 7, 2021 10:31 PM
> To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [pull-request] next-crypto 21.08 rc1
> 

<snip>

>       crypto/cnxk: add IPsec datapath

I don't have this patch in my inbox to reply to, but I think it's causing the following build failure in main (02edbfab1e):
"""
$ meson --werror -Dc_args='-DRTE_ENABLE_ASSERT' --buildtype=debug build && ninja -C build
...
../../root/dpdk/drivers/crypto/cnxk/cn10k_cryptodev_ops.c: In function 'cn10k_cpt_sec_post_process':
../../root/dpdk/drivers/crypto/cnxk/cn10k_cryptodev_ops.c:260:37: error: 'IPV6_VERSION' undeclared (first use in this function); did you mean 'IPVERSION'?
  260 |         RTE_IPV4_IHL_MULTIPLIER) == IPV6_VERSION);
"""

OS: Ubuntu 18.04.5
Meson: 0.58.1
Ninja: 1.8.2
Gcc: 7.5.0

Regards,
Ali

  parent reply	other threads:[~2021-07-08 17:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 19:30 Akhil Goyal
2021-07-07 21:57 ` Thomas Monjalon
2021-07-08  7:39   ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-08  7:41   ` [dpdk-dev] " Thomas Monjalon
2021-07-08  7:47     ` David Marchand
2021-07-08  7:48     ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-08 17:13 ` Ali Alnubani [this message]
2021-07-08 20:16   ` [dpdk-dev] " David Marchand
2021-07-09  4:24     ` [dpdk-dev] [EXT] " Anoob Joseph
2021-07-09  6:43       ` David Marchand
2021-07-09  9:00         ` Anoob Joseph

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=DM4PR12MB51678615814B51DAE8D0944CDA199@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@oss.nvidia.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=ktejasree@marvell.com \
    --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).