patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Anoob Joseph <anoobj@marvell.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
	Fan Zhang <fanzhang.oss@gmail.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Tejasree Kondoj <ktejasree@marvell.com>,
	Ciara Power <ciara.power@intel.com>
Subject: RE: [EXT] [PATCH v1 1/1] test: fix named test macro
Date: Wed, 23 Aug 2023 10:51:53 +0000	[thread overview]
Message-ID: <PH0PR18MB46727D3CFC8B6F8906D46688DF1CA@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <eeb20d3c3bdc748fade876c546186dae759815bf.1692784828.git.anatoly.burakov@intel.com>

> Currently, the TEST_CASE_NAMED_ST macro is implemented in a way that is
> identical to TEST_CASE_NAMED_WITH_DATA. In particular, it expects the
> test function to have a data argument, which is why a bunch of tests have an
> unused data arguments.
> 
> Fix this by adjusting the macro to not expect a test function with data
> arguments, and adjust the dependant test cases accordingly.
> 
> Fixes: 474f12024dd9 ("test/crypto: add lookaside IPsec cases")
> Cc: anoobj@marvell.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
>  app/test/test.h                        |  2 +-
>  app/test/test_cryptodev.c              | 74 ++++++++++++------------
>  app/test/test_security_inline_macsec.c | 48 ++++++++--------
> app/test/test_security_inline_proto.c  | 78 +++++++++++++-------------
>  4 files changed, 101 insertions(+), 101 deletions(-)
> 

Acked-by: Anoob Joseph <anoobj@marvell.com>



  parent reply	other threads:[~2023-08-23 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 10:00 Anatoly Burakov
2023-08-23 10:05 ` [EXT] " Akhil Goyal
2023-08-23 10:11 ` Hemant Agrawal
2023-08-23 10:51 ` Anoob Joseph [this message]
2023-09-06  8:28   ` [EXT] " 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=PH0PR18MB46727D3CFC8B6F8906D46688DF1CA@PH0PR18MB4672.namprd18.prod.outlook.com \
    --to=anoobj@marvell.com \
    --cc=anatoly.burakov@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ktejasree@marvell.com \
    --cc=stable@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).