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 1/2] userspace_ethtool: update test plan.
Date: Mon, 16 Jan 2017 08:52:49 +0000 [thread overview]
Message-ID: <B8B15C44A3F2C044966E545C7B73711539FB7969@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1484555392-32241-2-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 1/2] userspace_ethtool: update test plan.
>
> From: yufengmx <yufengx.mo@intel.com>
>
>
> *. add nic's firmware/bus-info information query checking
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
> ---
> test_plans/userspace_ethtool_test_plan.rst | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/test_plans/userspace_ethtool_test_plan.rst b/test_plans/userspace_ethtool_test_plan.rst
> index 83e7fac..498cc38 100644
> --- a/test_plans/userspace_ethtool_test_plan.rst
> +++ b/test_plans/userspace_ethtool_test_plan.rst
> @@ -65,8 +65,12 @@ dumped information, which are dumped separately by dpdk's ethtool and
> linux's ethtool, were exactly the same.
>
> EthApp> drvinfo
> - Port 0 driver: rte_ixgbe_pmd (ver: RTE 2.1.0)
> - Port 1 driver: rte_ixgbe_pmd (ver: RTE 2.1.0)
> + Port 0 driver: net_ixgbe (ver: DPDK 17.02.0-rc0)
> + bus-info: 0000:84:00.0
> + firmware-version: 0x61bf0001
> + Port 1 driver: net_ixgbe (ver: DPDK 17.02.0-rc0)
> + bus-info: 0000:84:00.1
> + firmware-version: 0x61bf0001
>
> Use "link" command to dump all ports link status.
> Notice:: On FVL, link detect need a physical link disconnect.
> --
> 1.9.3
next prev parent reply other threads:[~2017-01-16 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 8:29 [dts] [PATCH V2 0/2] userspace_ethtool: update automation testing script/test plan 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 [this message]
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 ` [dts] [PATCH V2 0/2] userspace_ethtool: update automation testing script/test plan Mo, YufengX
-- strict thread matches above, loose matches on Subject: below --
2017-01-16 8:13 Yufen Mo
2017-01-16 8:13 ` [dts] [PATCH V2 1/2] userspace_ethtool: update 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=B8B15C44A3F2C044966E545C7B73711539FB7969@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).