From: "Peng, Yuan" <yuan.peng@intel.com>
To: "Jiang, YuX" <yux.jiang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1 3/3] tests/generic_flow_api: add case:test_fdir_for_match_report
Date: Mon, 25 Oct 2021 09:06:34 +0000 [thread overview]
Message-ID: <CO1PR11MB5058DB91B93E4119B8569E12FE839@CO1PR11MB5058.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR11MB5150AFE34EB7E2AA0BC1CD49FE839@SJ0PR11MB5150.namprd11.prod.outlook.com>
Acked-by Peng, Yuan <yuan.peng@intel.com>
-----Original Message-----
From: Jiang, YuX <yux.jiang@intel.com>
Sent: Monday, October 25, 2021 3:24 PM
To: dts@dpdk.org; Peng, Yuan <yuan.peng@intel.com>
Subject: RE: [dts][PATCH V1 3/3] tests/generic_flow_api: add case:test_fdir_for_match_report
> -----Original Message-----
> From: Jiang, YuX <yux.jiang@intel.com>
> Sent: Monday, October 25, 2021 2:25 PM
> To: dts@dpdk.org; Peng, Yuan <yuan.peng@intel.com>
> Cc: Jiang, YuX <yux.jiang@intel.com>
> Subject: [dts][PATCH V1 3/3] tests/generic_flow_api: add
> case:test_fdir_for_match_report
>
> add case test_fdir_for_match_report
>
> Signed-off-by: Yu Jiang <yux.jiang@intel.com>
Tested-by: Yu Jiang <yux.jiang@intel.com>
next prev parent reply other threads:[~2021-10-25 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 6:24 [dts] [PATCH V1 0/3] tests/generic_flow_api: add fdir's case Yu Jiang
2021-10-25 6:24 ` [dts] [PATCH V1 1/3] test_plans/fdir: move case: fdir for Control levels of FDir match reporting to generic_flow_api Yu Jiang
2021-10-25 6:24 ` [dts] [PATCH V1 2/3] test_plans/generic_flow_api: add case: fdir for Control levels of FDir match reporting Yu Jiang
2021-10-25 6:24 ` [dts] [PATCH V1 3/3] tests/generic_flow_api: add case:test_fdir_for_match_report Yu Jiang
2021-10-25 7:23 ` Jiang, YuX
2021-10-25 9:06 ` Peng, Yuan [this message]
2021-10-27 6:14 ` Tu, Lijuan
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=CO1PR11MB5058DB91B93E4119B8569E12FE839@CO1PR11MB5058.namprd11.prod.outlook.com \
--to=yuan.peng@intel.com \
--cc=dts@dpdk.org \
--cc=yux.jiang@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).