test suite reviews and discussions
 help / color / mirror / Atom feed
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 V3 3/3] tests/vhost_cbdma: modify test suite sync with test plan change
Date: Wed, 26 Jan 2022 08:31:33 +0000	[thread overview]
Message-ID: <564e7f9f7b774418ac3ca8f4da899690@intel.com> (raw)
In-Reply-To: <20220122051050.2275833-1-weix.ling@intel.com>

> -----Original Message-----
> From: Wei Ling <weix.ling@intel.com>
> Sent: 2022年1月22日 13:11
> To: dts@dpdk.org
> Cc: Ling, WeiX <weix.ling@intel.com>
> Subject: [dts][PATCH V3 3/3] tests/vhost_cbdma: modify test suite sync with test
> plan change
> 
> v1:
> conf/vhost_cbdma: modify config sync with test plan change.
> test_plans/vhost_cbdma_test_plan: modify test plan to coverage more test
> point.
> tests/vhost_cbdma: modify test suite sync with test plan change.
> v2:
> test_plans/vhost_cbdma_test_plan: fix test plan make html format issue.
> v3:
> tests/vhost_cbdma: add '--force-max-simd-bitwidth=512' param in case3.
> 
> Signed-off-by: Wei Ling <weix.ling@intel.com>

The commit message is used to introduce the patch not the series.
The cover letter is used to introduce the series.

For example, this patch is about tests/vhost_cbdma, 
it don't have any change to conf/vhost_cbdma and test_plans/vhost_cbdma_test_plan

Please revise your commit message to match the patch, not the series. Thanks.



      reply	other threads:[~2022-01-26  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22  5:10 Wei Ling
2022-01-26  8:31 ` Tu, Lijuan [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=564e7f9f7b774418ac3ca8f4da899690@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).