From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xu, Ke1" <ke1.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>, "Fu, Qi" <qi.fu@intel.com>
Subject: RE: [DTS][PATCH V2 0/4] update existing cases and add new sub-cases to validate port representor action and represented port action
Date: Thu, 22 Dec 2022 07:45:26 +0000 [thread overview]
Message-ID: <CY5PR11MB618732316B587F94745BE31EF5E89@CY5PR11MB6187.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221221101252.59230-1-ke1.xu@intel.com>
> -----Original Message-----
> From: Xu, Ke1 <ke1.xu@intel.com>
> Sent: Wednesday, December 21, 2022 6:13 PM
> To: dts@dpdk.org
> Cc: Tu, Lijuan <lijuan.tu@intel.com>; Peng, Yuan <yuan.peng@intel.com>;
> Fu, Qi <qi.fu@intel.com>; Xu, Ke1 <ke1.xu@intel.com>
> Subject: [DTS][PATCH V2 0/4] update existing cases and add new sub-cases
> to validate port representor action and represented port action
>
> Deprecated TO_VF action contains a 'vf original' action which is not covered
> in previous tests. This patch applys equivilant 'vf original' rule to previous
> cases for 'vf id' action to cover 'vf original' action.
>
> This patch adds the following subcases to cover the negative scenario of
> 'port representor' action and 'represented port' action replacing 'vf
> original' action and 'vf id' action.
>
> 1. Add second PF with VFs for following cases 2. Add a subcase to validate
> creating 'represented port' action on a representor 3. Add a subcase to
> validate creating 'represented port' action on a VF 4. Add a subcase to
> validate creating 'represented port' action to a VF 5. Add two subcases to
> validate creating 'represented port' action to DCFs 6. Add a subcase to
> validate creating 'represented port' action to a representor of another DCF
> 7. Add a subcase to validate creating 'port representor' action on a
> representor 8. Add a subcase to validate creating 'port representor' action
> on a VF 9. Add a subcase to validate creating 'port representor' action to a
> VF 10. Add a subcase to validate creating 'port representor' action to a
> representor 11. Add a subcase to validate creating 'port representor' action
> to another DCF 12. Add a subcase to validate deprecated action 13. Add a
> subcase to validate using an invalid port id
>
> Ke Xu (4):
> test_plans/ice_dcf_switch_filter: update existing negative cases to
> validate represented port action and port representor action
> test_plans/ice_dcf_switch_filter: update existing TO_VF action cases
> to cover port representor action from not covered vf original action
> tests/ice_dcf_switch_filter: update existing TO_VF action cases to
> cover port representor action from not covered vf original action
> tests/ice_dcf_switch_filter: update existing negative cases to
> validate represented port action and port representor action
Applied, thanks
prev parent reply other threads:[~2022-12-22 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 10:12 Ke Xu
2022-12-21 10:12 ` [DTS][PATCH V2 1/4] test_plans/ice_dcf_switch_filter: update existing negative cases to validate represented port action and port representor action Ke Xu
2022-12-21 10:12 ` [DTS][PATCH V2 2/4] test_plans/ice_dcf_switch_filter: update existing TO_VF action cases to cover port representor action from not covered vf original action Ke Xu
2022-12-21 10:12 ` [DTS][PATCH V2 3/4] tests/ice_dcf_switch_filter: " Ke Xu
2022-12-21 10:12 ` [DTS][PATCH V2 4/4] tests/ice_dcf_switch_filter: update existing negative cases to validate represented port action and port representor action Ke Xu
2022-12-22 4:07 ` Peng, Yuan
2022-12-21 10:38 ` [DTS][PATCH V2 0/4] update existing cases and add new sub-cases to validate port representor action and represented port action Xu, Ke1
2022-12-22 7:45 ` 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=CY5PR11MB618732316B587F94745BE31EF5E89@CY5PR11MB6187.namprd11.prod.outlook.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=ke1.xu@intel.com \
--cc=qi.fu@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).