From: Akhil Goyal <gakhil@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Ciara Power <ciara.power@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"aconole@redhat.com" <aconole@redhat.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
Anoob Joseph <anoobj@marvell.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"asomalap@amd.com" <asomalap@amd.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"g.singh@nxp.com" <g.singh@nxp.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH v4 0/7] test: refactor crypto unit test framework
Date: Wed, 12 May 2021 16:06:12 +0000 [thread overview]
Message-ID: <MW2PR18MB2284AE3C1315185F6E89322AD8529@MW2PR18MB2284.namprd18.prod.outlook.com> (raw)
In-Reply-To: <4347689.mQGEhl1lfM@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, May 12, 2021 9:35 PM
> To: Ciara Power <ciara.power@intel.com>; Akhil Goyal
> <gakhil@marvell.com>
> Cc: dev@dpdk.org; declan.doherty@intel.com; aconole@redhat.com;
> hemant.agrawal@nxp.com; Anoob Joseph <anoobj@marvell.com>;
> ruifeng.wang@arm.com; asomalap@amd.com;
> ajit.khaparde@broadcom.com; g.singh@nxp.com; roy.fan.zhang@intel.com
> Subject: Re: [dpdk-dev] [EXT] [PATCH v4 0/7] test: refactor crypto unit test
> framework
>
> 12/05/2021 18:00, Akhil Goyal:
> > > I see this patchset is merged in the crypto tree but I guess it is not
> definitive.
> > > Am I right it is too late to do such refactoring after -rc2?
> > > What is the intent?
> > >
> > The case is not failing in my testing. Neither it is reproducible at Ciara's end.
> > Ciara has asked to rerun the CI to check if it is false positive.
> > I don't want to defer this series as it passes all test except the CI and has
> been
> > Reviewed by multiple people.
> > I am merging this patch for RC2. If there is any issue, it can be fixed in RC3
>
> -rc2 was closed last week. I am supposed to close -rc3 today.
> Do you confirm it is OK to pull today?
>
Yes you can pull in 30 mins.
I meant RC3 . 😊
next prev parent reply other threads:[~2021-05-12 16:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 11:36 [dpdk-dev] " Ciara Power
2021-05-12 11:36 ` [dpdk-dev] [PATCH v4 1/7] app/test: refactor of unit test suite runner Ciara Power
2021-05-12 11:36 ` [dpdk-dev] [PATCH v4 2/7] test: introduce parent testsuite format Ciara Power
2021-05-12 11:36 ` [dpdk-dev] [PATCH v4 3/7] test/crypto: refactor to use sub-testsuites Ciara Power
2021-05-12 11:36 ` [dpdk-dev] [PATCH v4 4/7] test/crypto: replace unsupported with skipped Ciara Power
2021-05-12 11:36 ` [dpdk-dev] [PATCH v4 5/7] test/crypto: move testsuite params to header file Ciara Power
2021-05-12 11:36 ` [dpdk-dev] [PATCH v4 6/7] test/crypto: fix return value on test skipped Ciara Power
2021-05-12 11:36 ` [dpdk-dev] [PATCH v4 7/7] test/crypto: dynamically build blockcipher suite Ciara Power
2021-05-12 13:15 ` [dpdk-dev] [EXT] [PATCH v4 0/7] test: refactor crypto unit test framework Akhil Goyal
2021-05-12 15:42 ` Thomas Monjalon
2021-05-12 16:00 ` Akhil Goyal
2021-05-12 16:05 ` Thomas Monjalon
2021-05-12 16:06 ` Akhil Goyal [this message]
2021-05-13 13:28 ` Aaron Conole
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=MW2PR18MB2284AE3C1315185F6E89322AD8529@MW2PR18MB2284.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=aconole@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anoobj@marvell.com \
--cc=asomalap@amd.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=roy.fan.zhang@intel.com \
--cc=ruifeng.wang@arm.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).