DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>,
	"Troy, Rebecca" <rebecca.troy@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"Coyle, David" <david.coyle@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] test/crypto: refactor DOCSIS to show hidden cases
Date: Wed, 3 Nov 2021 18:56:48 +0000	[thread overview]
Message-ID: <CO6PR18MB44848FB080275B81E4E37D80D88C9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MN2PR11MB3821AA5293DF5BD7B24CB059E68B9@MN2PR11MB3821.namprd11.prod.outlook.com>

> >In the current implementation, the DOCSIS test cases are running and being
> >reported as one test, despite the fact that multiple test cases are hidden
> >inside i.e. "test_DOCSIS_PROTO_all" runs
> >52 test cases. Each DOCSIS test case should be reported individually instead.
> >
> >This commit achieves this by removing the use of the
> test_DOCSIS_PROTO_all
> >function and statically listing the test cases to run when building the test
> suite,
> >which are then reported to the user by description.
> >
> >Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
> >
> Acked-by: Ciara Power <ciara.power@intel.com>

Acked-by: Akhil Goyal <gakhil@marvell.com>

Applied to dpdk-next-crypto

Thanks.

  reply	other threads:[~2021-11-03 18:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 10:53 [dpdk-dev] [PATCH] test/crypto: refactor docsis " Rebecca Troy
2021-10-28 10:34 ` Coyle, David
2021-10-28 10:41   ` Troy, Rebecca
2021-10-29  9:04 ` [dpdk-dev] [PATCH v2] test/crypto: refactor DOCSIS " Rebecca Troy
2021-11-02 10:40   ` Power, Ciara
2021-11-03 18:56     ` Akhil Goyal [this message]
2021-11-02 10:46   ` Coyle, David

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=CO6PR18MB44848FB080275B81E4E37D80D88C9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=david.coyle@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=rebecca.troy@intel.com \
    --cc=roy.fan.zhang@intel.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).