test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH 0/4] add unified packet type module and test suite
Date: Wed, 16 Sep 2015 13:03:58 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10EF4EC7@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1442393812-30481-1-git-send-email-yufengx.mo@intel.com>

Hi Yufen,
Would you please add more descriptions of this patch set? As an sample, explain what's the basic concept of this feature.

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yufen Mo
> Sent: Wednesday, September 16, 2015 4:57 PM
> To: dts@dpdk.org
> Cc: yufengmx
> Subject: [dts] [PATCH 0/4] add unified packet type module and test suite
> 
> From: yufengmx <yufengmx.mo@intel.com>
> 
> 
> yufengmx (4):
>   unified packet type test suite implementation
>   fix issue test plan for unified packet type
>   Add test suite for unified packet type
>   Update lldp and nvgre layer module
> 
>  dep/lldp.py                      | 242 +++++++++++++++
>  framework/packet.py              | 642
> +++++++++++++++++++++++++++++++++++++++
>  test_plans/uni_pkt_test_plan.rst |  30 +-
>  tests/TestSuite_uni_pkt.py       | 364 ++++++++++++++++++++++
>  4 files changed, 1262 insertions(+), 16 deletions(-)
>  create mode 100644 dep/lldp.py
>  create mode 100755 framework/packet.py
>  create mode 100644 tests/TestSuite_uni_pkt.py
> 
> --
> 1.9.3

      parent reply	other threads:[~2015-09-16 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  8:56 Yufen Mo
2015-09-16  8:56 ` [dts] [PATCH 1/4] " Yufen Mo
2015-09-16 13:00   ` Liu, Yong
2015-09-16  8:56 ` [dts] [PATCH 2/4] " Yufen Mo
2015-09-16  8:56 ` [dts] [PATCH 3/4] " Yufen Mo
2015-09-16  8:56 ` [dts] [PATCH 4/4] " Yufen Mo
2015-09-16 13:03 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E10EF4EC7@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yufengx.mo@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).