test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Chu, Haijun" <haijun.chu@intel.com>
To: "Han, YingyaX" <yingyax.han@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Han, YingyaX" <yingyax.han@intel.com>
Subject: RE: [dts][PATCH V1 9/9]test_plans: add the index of test plan
Date: Thu, 5 Jan 2023 01:58:18 +0000	[thread overview]
Message-ID: <BYAPR11MB2663CEB58FBFAFFA1041A66F8EFA9@BYAPR11MB2663.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230103083951.1553786-10-yingyax.han@intel.com>

Acked-by: Haijun Chu<haijun.chu@intel.com>

-----Original Message-----
From: Yingya Han <yingyax.han@intel.com> 
Sent: Tuesday, January 3, 2023 4:40 PM
To: dts@dpdk.org
Cc: Han, YingyaX <yingyax.han@intel.com>
Subject: [dts][PATCH V1 9/9]test_plans: add the index of test plan

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 


      reply	other threads:[~2023-01-05  1:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03  8:39 [dts][PATCH V1 0/9]test_plans: add perf test plans Yingya Han
2023-01-03  8:39 ` [dts][PATCH V1 1/9]test_plans: add l3fwd_lpm_ipv4_rfc2544 test plan Yingya Han
2023-01-03  8:39 ` [dts][PATCH V1 2/9]test_plans: add l3fwd_lpm_ipv6 " Yingya Han
2023-01-03  8:39 ` [dts][PATCH V1 3/9]test_plans: add testpmd_perf " Yingya Han
2023-01-03  8:39 ` [dts][PATCH V1 4/9]test_plans: add vf_l3fwd_em_kernelpf " Yingya Han
2023-01-03  8:39 ` [dts][PATCH V1 5/9]test_plans: add vf_l3fwd_kernelpf " Yingya Han
2023-01-03  8:39 ` [dts][PATCH V1 6/9]test_plans: add vf_l3fwd_lpm_ipv4_kernelpf " Yingya Han
2023-01-03  8:39 ` [dts][PATCH V1 7/9]test_plans: add vf_l3fwd_lpm_ipv4_rfc2544_kernelpf " Yingya Han
2023-01-03  8:39 ` [dts][PATCH V1 8/9]test_plans: add vf_l3fwd_lpm_ipv6_kernelpf " Yingya Han
2023-01-05 14:25   ` lijuan.tu
2023-01-03  8:39 ` [dts][PATCH V1 9/9]test_plans: add the index of " Yingya Han
2023-01-05  1:58   ` Chu, Haijun [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=BYAPR11MB2663CEB58FBFAFFA1041A66F8EFA9@BYAPR11MB2663.namprd11.prod.outlook.com \
    --to=haijun.chu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yingyax.han@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).