From: Shally Verma <shallyv@marvell.com>
To: "Trybula, ArturX" <arturx.trybula@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
Ashish Gupta <ashishg@marvell.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH v3 1/1] test/compress: unit tests refactoring
Date: Wed, 6 Nov 2019 15:36:17 +0000 [thread overview]
Message-ID: <BN8PR18MB28677C49AA494D3030EDDD4BAD790@BN8PR18MB2867.namprd18.prod.outlook.com> (raw)
In-Reply-To: <5B6D1C77E9D7034C93E97BD83D1D9F572F2328AC@hasmsx107.ger.corp.intel.com>
> -----Original Message-----
> From: Trybula, ArturX <arturx.trybula@intel.com>
> Sent: Wednesday, November 6, 2019 9:03 PM
> To: Shally Verma <shallyv@marvell.com>; dev@dpdk.org; Trahe, Fiona
> <fiona.trahe@intel.com>; Dybkowski, AdamX
> <adamx.dybkowski@intel.com>; akhil.goyal@nxp.com; Ashish Gupta
> <ashishg@marvell.com>
> Subject: RE: [EXT] [PATCH v3 1/1] test/compress: unit tests refactoring
>
..
> My suggestion was to move extbuf_info, out_of_space_zlib too to priv_data
> .. but its just suggestion... you can ignore If it complicate the purpose [Artur]
> Ok. I'll try to optimize the list of params.
>
> [Artur] Shally, I assume all the issues can be closed and V4 can be prepared
> tomorrow?
>
[Shally] Yes.
> > ...
> ...
> > > > 2.17.1
next prev parent reply other threads:[~2019-11-06 15:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 14:45 [dpdk-dev] [PATCH] test/compress: unit tests refactoring Artur Trybula
2019-09-12 14:34 ` [dpdk-dev] [PATCH v2 0/1] compression: " Artur Trybula
2019-09-12 14:34 ` [dpdk-dev] [PATCH v2 1/1] test/compress: " Artur Trybula
2019-10-24 9:16 ` [dpdk-dev] [PATCH v3 0/1] compression: " Artur Trybula
2019-10-24 9:16 ` [dpdk-dev] [PATCH v3 1/1] test/compress: " Artur Trybula
2019-10-24 9:22 ` Dybkowski, AdamX
2019-10-24 9:27 ` Akhil Goyal
2019-10-31 8:38 ` Akhil Goyal
2019-10-31 18:23 ` [dpdk-dev] [EXT] " Shally Verma
2019-11-04 10:24 ` Trybula, ArturX
2019-11-04 15:24 ` Shally Verma
2019-11-06 7:43 ` Akhil Goyal
2019-11-06 11:33 ` Trybula, ArturX
2019-11-06 15:00 ` Shally Verma
2019-11-06 15:33 ` Trybula, ArturX
2019-11-06 15:36 ` Shally Verma [this message]
2019-11-07 17:26 ` [dpdk-dev] [PATCH v4 0/1] compression: " Artur Trybula
2019-11-07 17:26 ` [dpdk-dev] [PATCH v4 1/1] test/compress: " Artur Trybula
2019-11-08 6:35 ` [dpdk-dev] [EXT] " Shally Verma
2019-11-08 10:16 ` Akhil Goyal
2019-11-08 18:40 ` [dpdk-dev] " Thomas Monjalon
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=BN8PR18MB28677C49AA494D3030EDDD4BAD790@BN8PR18MB2867.namprd18.prod.outlook.com \
--to=shallyv@marvell.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arturx.trybula@intel.com \
--cc=ashishg@marvell.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.