test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Chen, LingliX" <linglix.chen@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: RE: [dts][PATCH V1 2/2] tests/l3fwdacl: merge l3fwd-acl with l3fwd and fix to support different force-max-simd-bitwidth
Date: Wed, 15 Jun 2022 08:52:44 +0000	[thread overview]
Message-ID: <SJ0PR11MB48933B9B0503825B9E21290A90AD9@SJ0PR11MB4893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220615124821.1582235-3-yux.jiang@intel.com>


> -----Original Message-----
> From: Jiang, YuX <yux.jiang@intel.com>
> Sent: Wednesday, June 15, 2022 8:48 PM
> To: Tu, Lijuan <lijuan.tu@intel.com>; dts@dpdk.org
> Cc: Jiang, YuX <yux.jiang@intel.com>; Chen, LingliX <linglix.chen@intel.com>
> Subject: [dts][PATCH V1 2/2] tests/l3fwdacl: merge l3fwd-acl with l3fwd and fix
> to support different force-max-simd-bitwidth
> 
> 1, According to dpdk22.07rc1 commit id 6de0ea50e("examples/l3fwd: merge
> l3fwd-acl example"), modify l3fwdacl suite.
> 2, Since DTS commit "7eaf4b60 tests/l3fwdacl: modify pmd param for acl" has
> incorrect usage,  fix script to support different rx_mode.
> 
> Signed-off-by: Lingli Chen <linglix.chen@intel.com>
> Signed-off-by: Yu Jiang <yux.jiang@intel.com>

Tested-by: Lingli Chen <linglix.chen@intel.com>

  reply	other threads:[~2022-06-15  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 12:48 [dts][PATCH V1 0/2] l3fwdacl: merge l3fwd-acl with l3fwd Yu Jiang
2022-06-15 12:48 ` [dts][PATCH V1 1/2] test_plans/l3fwdacl: " Yu Jiang
2022-06-15 12:48 ` [dts][PATCH V1 2/2] tests/l3fwdacl: merge l3fwd-acl with l3fwd and fix to support different force-max-simd-bitwidth Yu Jiang
2022-06-15  8:52   ` Chen, LingliX [this message]
2022-06-15  9:07   ` lijuan.tu
2022-06-21  7:13   ` lijuan.tu

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=SJ0PR11MB48933B9B0503825B9E21290A90AD9@SJ0PR11MB4893.namprd11.prod.outlook.com \
    --to=linglix.chen@intel.com \
    --cc=dts@dpdk.org \
    /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).