From: "Peng, Yuan" <yuan.peng@intel.com>
To: "Huang, ZhiminX" <zhiminx.huang@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Huang, ZhiminX" <zhiminx.huang@intel.com>
Subject: RE: [dts][PATCH V1 6/6] conf/*:add config file for new suites
Date: Fri, 9 Jun 2023 09:22:06 +0000 [thread overview]
Message-ID: <CO1PR11MB5058D530010FFDCA0747FC7EFE51A@CO1PR11MB5058.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230608182742.360594-7-zhiminx.huang@intel.com>
> -----Original Message-----
> From: Zhimin Huang <zhiminx.huang@intel.com>
> Sent: Friday, June 9, 2023 2:28 AM
> To: dts@dpdk.org
> Cc: Huang, ZhiminX <zhiminx.huang@intel.com>
> Subject: [dts][PATCH V1 6/6] conf/*:add config file for new suites
>
> add config file for new test suites
>
> Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
> ---
Acked-by: Peng, Yuan <yuan.peng@intel.com>
prev parent reply other threads:[~2023-06-09 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 18:27 [dts][PATCH V1 0/6] add new common module and add " Zhimin Huang
2023-06-08 18:27 ` [dts][PATCH V1 1/6] tests/func_test_base:add new commom module to refactor func test cases Zhimin Huang
2023-06-08 18:27 ` [dts][PATCH V1 2/6] tests/kernelpf_vf:add new suite to cover most of the basic vf cases Zhimin Huang
2023-06-14 2:03 ` Tu, Lijuan
2023-06-08 18:27 ` [dst][PATCH V1 3/6] test_plans/kernelpf_vf_test_plan:add new plan " Zhimin Huang
2023-06-08 18:27 ` [dts][PATCH V1 4/6] tests/ice_kernelpf_dcf:add new suite to cover dcf pmd function Zhimin Huang
2023-06-08 18:27 ` [dst][PATCH V1 5/6] test_plans/ice_kernelpf_dcf_test_plan:add new plan to cover the most of " Zhimin Huang
2023-06-08 18:27 ` [dts][PATCH V1 6/6] conf/*:add config file for new suites Zhimin Huang
2023-06-09 9:22 ` Peng, Yuan [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=CO1PR11MB5058D530010FFDCA0747FC7EFE51A@CO1PR11MB5058.namprd11.prod.outlook.com \
--to=yuan.peng@intel.com \
--cc=dts@dpdk.org \
--cc=zhiminx.huang@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).