From: "Daly, Lee" <lee.daly@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] test/compress: add mbuf offset unit test
Date: Mon, 25 Feb 2019 09:39:15 +0000 [thread overview]
Message-ID: <F5C6929789601049BEB7272E267355988593C7@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <1984658.sT1rjRnIyj@xps>
Not in its current state.
-Fiona: Does the current team plan on sending another version of membuf_offset UT for 19.05?
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Monday, February 25, 2019 9:32 AM
> To: Daly, Lee <lee.daly@intel.com>
> Cc: dev@dpdk.org; akhil.goyal@nxp.com; Jozwiak, TomaszX
> <tomaszx.jozwiak@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v3] test/compress: add mbuf offset unit test
>
> 25/02/2019 09:56, Daly, Lee:
> > Hi Thomas,
> > This patch was deferred to a later release, Patchwork did not reflect
> > this so I have now changed it.
>
> You mean you don't want this patch in DPDK 19.05?
>
>
prev parent reply other threads:[~2019-02-25 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 14:06 [dpdk-dev] [PATCH] test/compress: add offset tests Lee Daly
2018-07-31 15:01 ` Thomas Monjalon
2018-07-31 15:05 ` Daly, Lee
2018-11-27 10:30 ` [dpdk-dev] [PATCH v2] test/compress: add mbuf offset unit test Lee Daly
2018-12-05 14:38 ` [dpdk-dev] [PATCH v3] " Lee Daly
2018-12-05 15:18 ` Jozwiak, TomaszX
2019-02-24 22:59 ` Thomas Monjalon
2019-02-25 8:56 ` Daly, Lee
2019-02-25 9:32 ` Thomas Monjalon
2019-02-25 9:39 ` Daly, Lee [this message]
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=F5C6929789601049BEB7272E267355988593C7@IRSMSX106.ger.corp.intel.com \
--to=lee.daly@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=thomas@monjalon.net \
--cc=tomaszx.jozwiak@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).