From: "Li, HongboX" <hongbox.li@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Cc: "Jiale, SongX" <songx.jiale@intel.com>
Subject: RE: [dts] [PATCH V2 3/3] tests/ice_iavf_flow_subscribe: add a suite to test ice iavf flow subscribe
Date: Mon, 5 Dec 2022 03:13:09 +0000 [thread overview]
Message-ID: <PH8PR11MB71207774E833176EC266B2D29F189@PH8PR11MB7120.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN0PR11MB5743823FD3E71FA78654045BE7189@BN0PR11MB5743.namprd11.prod.outlook.com>
-----Original Message-----
From: Jiale, SongX <songx.jiale@intel.com>
Sent: 2022年12月5日 10:18
To: Li, HongboX <hongbox.li@intel.com>
Subject: FW: [dts] [PATCH V2 3/3] tests/ice_iavf_flow_subscribe: add a suite to test ice iavf flow subscribe
-----Original Message-----
From: Jiale, SongX <songx.jiale@intel.com>
Sent: Wednesday, November 30, 2022 2:23 AM
To: dts@dpdk.org
Cc: Jiale, SongX <songx.jiale@intel.com>
Subject: [dts] [PATCH V2 3/3] tests/ice_iavf_flow_subscribe: add a suite to test ice iavf flow subscribe
add suite to test the dpdk-22.11 new feaute of iavf subscribes to the pf flow.
Signed-off-by: Song Jiale <songx.jiale@intel.com>
---
Tested-by: Hongbo Li < hongbox.li@intel.com>
prev parent reply other threads:[~2022-12-05 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 18:23 [PATCH V2 0/3] add ice_iavf_flow_subscribe Song Jiale
2022-11-29 18:23 ` [dts] [PATCH V2 1/3] test_plans/index.rst: add ice_iavf_flow_subscribe test plan Song Jiale
2022-11-29 18:23 ` [dts] [PATCH V2 2/3] test_plans/ice_iavf_flow_subscribe: add a testplan to test ice iavf flow subscribe Song Jiale
2022-11-29 18:23 ` [dts] [PATCH V2 3/3] tests/ice_iavf_flow_subscribe: add a suite " Song Jiale
2022-11-30 7:19 ` Peng, Yuan
[not found] ` <BN0PR11MB5743823FD3E71FA78654045BE7189@BN0PR11MB5743.namprd11.prod.outlook.com>
2022-12-05 3:13 ` Li, HongboX [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=PH8PR11MB71207774E833176EC266B2D29F189@PH8PR11MB7120.namprd11.prod.outlook.com \
--to=hongbox.li@intel.com \
--cc=dts@dpdk.org \
--cc=songx.jiale@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).