test suite reviews and discussions
 help / color / mirror / Atom feed
From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lei.a.yao@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V4 0/3] tests/malicious_driver_event_indication: upload test plan and automation script
Date: Tue, 26 May 2020 14:25:58 +0800	[thread overview]
Message-ID: <20200526062601.17135-1-yufengx.mo@intel.com> (raw)

 Malicious driver event indication process in FVL PF driver. 

v4: 
 -  fix typo in test plan. 

v3: 
 -  rebase source code. 

v2: 
 -  change auto patch dpdk code method 

yufengmx (3):
  tests/malicious_driver_event_indication: upload automation script
  tests/malicious_driver_event_indication: update test plan
  tests/malicious_driver_event_indication: add test plan index

 test_plans/index.rst                          |   1 +
 ...ious_driver_event_indication_test_plan.rst |  96 +++++
 ...Suite_malicious_driver_event_indication.py | 335 ++++++++++++++++++
 3 files changed, 432 insertions(+)
 create mode 100644 test_plans/malicious_driver_event_indication_test_plan.rst
 create mode 100644 tests/TestSuite_malicious_driver_event_indication.py

-- 
2.21.0


             reply	other threads:[~2020-05-26  6:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  6:25 yufengmx [this message]
2020-05-26  6:25 ` [dts] [PATCH V4 1/3] tests/malicious_driver_event_indication: upload automation yufengmx
2020-05-26  6:26 ` [dts] [PATCH V4 2/3] tests/malicious_driver_event_indication: update test plan yufengmx
2020-05-26  6:26 ` [dts] [PATCH V4 3/3] tests/malicious_driver_event_indication: add " yufengmx
2020-06-01  3:13 ` [dts] [PATCH V4 0/3] tests/malicious_driver_event_indication: upload test plan and automation script Tu, Lijuan

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=20200526062601.17135-1-yufengx.mo@intel.com \
    --to=yufengx.mo@intel.com \
    --cc=dts@dpdk.org \
    --cc=lei.a.yao@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).