From: "Mo, YufengX" <yufengx.mo@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V2 0/2] userspace_ethtool: update automation testing script/test plan
Date: Mon, 16 Jan 2017 08:52:59 +0000 [thread overview]
Message-ID: <B8B15C44A3F2C044966E545C7B73711539FB7978@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1484555392-32241-1-git-send-email-yufengx.mo@intel.com>
ignore this mail.
> -----Original Message-----
> From: Mo, YufengX
> Sent: January 16, 2017 4:30 PM
> To: dts@dpdk.org
> Cc: Mo, YufengX
> Subject: [dts][PATCH V2 0/2] userspace_ethtool: update automation testing script/test plan
>
> From: yufengmx <yufengx.mo@intel.com>
>
> *.add nic's firmware/bus-info information query checking, which is corresponding with Qiming Yang's patchset 18597-18600 patchset
> 18601
>
> yufengmx (2):
> userspace_ethtool: update test plan.
> userspace_ethtool: update automation testing script.
>
> test_plans/userspace_ethtool_test_plan.rst | 8 +-
> tests/TestSuite_userspace_ethtool.py | 141 +++++++++++++++++++++++------
> 2 files changed, 117 insertions(+), 32 deletions(-)
>
> --
> 1.9.3
next prev parent reply other threads:[~2017-01-16 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 8:29 yufengx.mo
2017-01-16 8:29 ` [dts] [PATCH V2 1/2] userspace_ethtool: update test plan yufengx.mo
2017-01-16 8:52 ` Mo, YufengX
2017-01-16 8:29 ` [dts] [PATCH V2 2/2] userspace_ethtool: update automation testing script yufengx.mo
2017-01-16 8:52 ` Mo, YufengX
2017-01-16 8:52 ` Mo, YufengX [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-16 8:13 [dts] [PATCH V2 0/2] userspace_ethtool: update automation testing script/test plan Yufen Mo
2017-01-16 8:21 ` Mo, YufengX
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=B8B15C44A3F2C044966E545C7B73711539FB7978@shsmsx102.ccr.corp.intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=yong.liu@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).