From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ling, WeiX" <weix.ling@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Ling, WeiX" <weix.ling@intel.com>
Subject: RE: [dts][PATCH V4 3/3] tests/vhost_cbdma: modify test suite sync with test plan change
Date: Sat, 29 Jan 2022 03:32:27 +0000 [thread overview]
Message-ID: <41a7d4b1c3f54755ab207d39cebc4bc1@intel.com> (raw)
In-Reply-To: <20220126092151.916483-1-weix.ling@intel.com>
> -----Original Message-----
> From: Wei Ling <weix.ling@intel.com>
> Sent: 2022年1月26日 17:22
> To: dts@dpdk.org
> Cc: Ling, WeiX <weix.ling@intel.com>
> Subject: [dts][PATCH V4 3/3] tests/vhost_cbdma: modify test suite sync with test
> plan change
>
> Modify test suite sync with test plan change.
> Add '--force-max-simd-bitwidth=512' param in case3.
> Add skip step when case running on 2M hugepage size testbed.
>
> Signed-off-by: Wei Ling <weix.ling@intel.com>
Series applied.
next prev parent reply other threads:[~2022-01-29 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 9:21 Wei Ling
2022-01-29 3:32 ` Tu, Lijuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-26 9:09 Lingli Chen
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=41a7d4b1c3f54755ab207d39cebc4bc1@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=weix.ling@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).