From: Akhil Goyal <gakhil@marvell.com>
To: Tejasree Kondoj <ktejasree@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
Ciara Power <ciara.power@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2] app/test: add external mbuf IPsec tests
Date: Tue, 19 Sep 2023 19:30:00 +0000 [thread overview]
Message-ID: <CO6PR18MB4484BB8CD43241FB4123D451D8FAA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230814064737.197477-1-ktejasree@marvell.com>
> Subject: [PATCH v2] app/test: add external mbuf IPsec tests
>
> Adding IPsec tests using external mbuf API.
>
> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
> ---
> v2:
> - Fixed compilation with ubuntu-20.04-gcc-static-i386.
Please rebase and fix compilation.
In file included from ../app/test/test_cryptodev.c:32:
../app/test/test_cryptodev.c:16331:4: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(const void *)’ [-Werror=incompatible-pointer-types]
16331 | test_ipsec_proto_sgl_ext_mbuf),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../app/test/test.h:130:22: note: in definition of macro ‘TEST_CASE_NAMED_ST’
130 | { setup, teardown, testcase, NULL, name, 1, NULL }
| ^~~~~~~~
../app/test/test_cryptodev.c:16331:4: note: (near initialization for ‘ipsec_proto_testsuite.unit_test_cases[90].testcase’)
16331 | test_ipsec_proto_sgl_ext_mbuf),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../app/test/test.h:130:22: note: in definition of macro ‘TEST_CASE_NAMED_ST’
130 | { setup, teardown, testcase, NULL, name, 1, NULL }
| ^~~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
next prev parent reply other threads:[~2023-09-19 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 9:42 [PATCH] " Tejasree Kondoj
2023-08-14 6:47 ` [PATCH v2] " Tejasree Kondoj
2023-08-17 5:37 ` Anoob Joseph
2023-09-19 19:30 ` Akhil Goyal [this message]
2023-09-20 7:22 ` [PATCH v3] " Tejasree Kondoj
2023-09-21 7:13 ` Akhil Goyal
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=CO6PR18MB4484BB8CD43241FB4123D451D8FAA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=ktejasree@marvell.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).