From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xu, HailinX" <hailinx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xu, HailinX" <hailinx.xu@intel.com>
Subject: Re: [dts] [PATCH v1]conf/test_case_checklist.json:carlsville not support cases.
Date: Mon, 20 Apr 2020 04:54:16 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC0CFD4@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1586746332-120212-1-git-send-email-hailinx.xu@intel.com>
Applied failed, please rework, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xu Hailin
> Sent: Monday, April 13, 2020 10:52 AM
> To: dts@dpdk.org
> Cc: Xu, HailinX <hailinx.xu@intel.com>
> Subject: [dts] [PATCH v1]conf/test_case_checklist.json:carlsville not support
> cases.
>
> From: xuhailin <hailinx.xu@intel.com>
>
> carlsville nic driver is i40e,so not support userspace_ethtool/port_mtu and
> userspace_ethtool/retrieve_reg.
>
> Signed-off-by: xuhailin <hailinx.xu@intel.com>
> ---
> conf/test_case_checklist.json | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 1a2d93ca..4dea9d90 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -1999,7 +1999,8 @@
> "fortville_25g",
> "fortpark",
> "fortpark_TLV",
> - "fortpark_TLV_vf"
> + "fortpark_TLV_vf",
> + "carlsville"
> ],
> "Target": [
> "ALL"
> @@ -2259,7 +2260,8 @@
> "fortpark_TLV_vf",
> "cavium_a064",
> "columbiaville_25g",
> - "columbiaville_100g"
> + "columbiaville_100g",
> + "carlsville"
> ],
> "Target": [
> "ALL"
> --
> 2.17.1
prev parent reply other threads:[~2020-04-20 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 2:52 Xu Hailin
2020-04-17 5:14 ` Zhao, XinfengX
2020-04-20 4:54 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BC0CFD4@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=hailinx.xu@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).