test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yufen Mo <yufengx.mo@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH V1 0/4] Add packet module and test suite for unified network packet function
Date: Wed, 23 Sep 2015 11:12:30 +0800	[thread overview]
Message-ID: <1442977954-15617-1-git-send-email-yufengx.mo@intel.com> (raw)

From: yufengmx <yufengx.mo@intel.com>

yufengmx (4):
  fix some issue of the test plan for unified packet type
  Add packet module for unified network packet function
  Add test suite for unified packet type     This suite validate unified
    packet type flag feature on different NICs. For     more details,
    please reference to test plan.
  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

             reply	other threads:[~2015-09-23  3:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23  3:12 Yufen Mo [this message]
2015-09-23  3:12 ` [dts] [PATCH V1 1/4] fix some issue of the test plan for unified packet type Yufen Mo
2015-09-23  3:12 ` [dts] [PATCH V1 2/4] Add packet module for unified network packet function Yufen Mo
2015-09-23  3:12 ` [dts] [PATCH V1 3/4] Add test suite for unified packet type This suite validate unified packet type flag feature on different NICs. For more details, please reference to test plan Yufen Mo
2015-09-23  3:12 ` [dts] [PATCH V1 4/4] Update lldp and nvgre layer module Yufen Mo
2015-09-23  7:13 [dts] [PATCH V1 0/4] Add packet module and test suite for unified network packet function Liu, Yong

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=1442977954-15617-1-git-send-email-yufengx.mo@intel.com \
    --to=yufengx.mo@intel.com \
    --cc=dts@dpdk.org \
    /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).