From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xiao, QimaiX" <qimaix.xiao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xiao, QimaiX" <qimaix.xiao@intel.com>
Subject: Re: [dts] [PATCH V1]conf/test_case_checklist.json: add cases not supported fortpark_TLV
Date: Wed, 27 Nov 2019 09:41:45 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB6987A@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1574819113-156755-1-git-send-email-qimaix.xiao@intel.com>
error: patch failed: conf/test_case_checklist.json:415
error: conf/test_case_checklist.json: patch does not apply
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xiao Qimai
> Sent: Wednesday, November 27, 2019 9:45 AM
> To: dts@dpdk.org
> Cc: Xiao, QimaiX <qimaix.xiao@intel.com>
> Subject: [dts] [PATCH V1]conf/test_case_checklist.json: add cases not
> supported fortpark_TLV
>
> test_flowctrl_off_pause_fwd_on and test_flowctrl_on_pause_fwd_on not
> support on fortpark_TLV
>
> Signed-off-by: Xiao Qimai <qimaix.xiao@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 ffafaf4..6e4f41c 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -415,7 +415,8 @@
> "fortville_spirit",
> "fortville_spirit_single",
> "fortville_25g",
> - "carlsville"
> + "carlsville",
> + "fortpark_TLV"
> ],
> "Target": [
> "ALL"
> @@ -451,7 +452,8 @@
> "fortville_spirit",
> "fortville_spirit_single",
> "fortville_25g",
> - "carlsville"
> + "carlsville",
> + "fortpark_TLV"
> ],
> "Target": [
> "ALL"
> --
> 1.8.3.1
prev parent reply other threads:[~2019-11-27 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 1:45 Xiao Qimai
2019-11-27 9:41 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB6987A@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=qimaix.xiao@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).