From: "Huang, ChenyuX" <chenyux.huang@intel.com>
To: "Chen, LingliX" <linglix.chen@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>,
"Chen, LingliX" <linglix.chen@intel.com>
Subject: RE: [dts][PATCH V1 3/3] tests/generic_flow_api: add case fdir_wrong_parameters sync with testplan
Date: Wed, 10 Aug 2022 09:05:17 +0000 [thread overview]
Message-ID: <PH0PR11MB5832399F619FD7E07267F822E0659@PH0PR11MB5832.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220802031310.5523-3-linglix.chen@intel.com>
> -----Original Message-----
> From: Lingli Chen <linglix.chen@intel.com>
> Sent: Tuesday, August 2, 2022 11:13 AM
> To: dts@dpdk.org
> Cc: Peng, Yuan <yuan.peng@intel.com>; Chen, LingliX <linglix.chen@intel.com>
> Subject: [dts][PATCH V1 3/3] tests/generic_flow_api: add case
> fdir_wrong_parameters sync with testplan
>
> 1. add i40e case fdir_wrong_parameters sync with testplan 2.
> test_fdir_for_flexbytes: remove Exceeds maximum payload limit rules test
> because incloud in case fdir_wrong_parameters.
>
> Signed-off-by: Lingli Chen <linglix.chen@intel.com>
> ---
Tested-by: Chenyu Huang <chenyux.huang@intel.com>
next prev parent reply other threads:[~2022-08-10 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 3:13 [dts][PATCH V1 1/3] test_plans/generic_flow_api: add i40e case fdir_for_vlan Lingli Chen
2022-08-02 3:13 ` [dts][PATCH V1 2/3] conf/test_case_checklist: add case fdir_wrong_parameters Lingli Chen
2022-08-30 6:06 ` Peng, Yuan
2022-08-02 3:13 ` [dts][PATCH V1 3/3] tests/generic_flow_api: add case fdir_wrong_parameters sync with testplan Lingli Chen
2022-08-10 9:05 ` Huang, ChenyuX [this message]
2022-08-30 6:06 ` Peng, Yuan
2022-09-07 9:12 ` lijuan.tu
2022-08-10 3:30 ` [dts][PATCH V1 1/3] test_plans/generic_flow_api: add i40e case fdir_for_vlan Peng, Yuan
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=PH0PR11MB5832399F619FD7E07267F822E0659@PH0PR11MB5832.namprd11.prod.outlook.com \
--to=chenyux.huang@intel.com \
--cc=dts@dpdk.org \
--cc=linglix.chen@intel.com \
--cc=yuan.peng@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).