From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xie, WeiX" <weix.xie@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xie, WeiX" <weix.xie@intel.com>
Subject: Re: [dts] [PATCH V1] conf/checklist:add not NIC supported
Date: Thu, 23 Apr 2020 05:52:54 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC0F1DC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1587535344-10184-1-git-send-email-weix.xie@intel.com>
Applied thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xie Wei
> Sent: Wednesday, April 22, 2020 2:02 PM
> To: dts@dpdk.org
> Cc: Xie, WeiX <weix.xie@intel.com>
> Subject: [dts] [PATCH V1] conf/checklist:add not NIC supported
>
> From: "Xie,WeiX" <weix.xie@intel.com>
>
> ixgbe not support sriov_kwm,vf_interrupt_pmd not support some nics.
>
> Signed-off-by: Xie,WeiX <weix.xie@intel.com>
> ---
> conf/test_case_checklist.json | 20 ++++++++++++++------
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index d29d235..cd5d01f 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2245,7 +2245,9 @@
> ],
> "NIC": [
> "niantic",
> - "sagepond"
> + "sagepond",
> + "sageville",
> + "twinpond"
> ],
> "Target": [
> "ALL"
> @@ -2513,7 +2515,9 @@
> ],
> "NIC": [
> "niantic",
> - "sagepond"
> + "sagepond",
> + "sageville",
> + "twinpond"
> ],
> "Target": [
> "ALL"
> @@ -2705,9 +2709,11 @@
> ],
> "NIC": [
> "niantic",
> - "sagepond",
> - "sageville",
> - "fortville_25g"
> + "sagepond",
> + "sageville",
> + "fortville_25g",
> + "twinpond",
> + "powerville"
> ],
> "Target": [
> "ALL"
> @@ -2725,7 +2731,9 @@
> "niantic",
> "sagepond",
> "sageville",
> - "fortville_25g"
> + "fortville_25g",
> + "twinpond",
> + "powerville"
> ],
> "Target": [
> "ALL"
> --
> 1.8.3.1
prev parent reply other threads:[~2020-04-23 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 6:02 Xie Wei
2020-04-23 5:52 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC0F1DC@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=weix.xie@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).