From: "Mo, YufengX" <yufengx.mo@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>, "Yao, Lei A" <lei.a.yao@intel.com>
Subject: Re: [dts] [PATCH V2 0/3] tests/malicious_driver_event_indication: upload test plan and automation script
Date: Wed, 6 May 2020 01:40:05 +0000 [thread overview]
Message-ID: <f614d029b5db4d49a4fa4b808646cd74@intel.com> (raw)
In-Reply-To: <20200430085518.31075-1-yufengx.mo@intel.com>
Tested by Mo, YufengX <yufengx.mo@intel.com>
> -----Original Message-----
> From: Mo, YufengX
> Sent: Thursday, April 30, 2020 4:55 PM
> To: dts@dpdk.org; Yao, Lei A <lei.a.yao@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts][PATCH V2 0/3] tests/malicious_driver_event_indication: upload test plan and automation script
>
> Malicious driver event indication process in FVL PF driver.
>
> 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 | 327 ++++++++++++++++++
> 3 files changed, 424 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
prev parent reply other threads:[~2020-05-06 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 8:55 yufengmx
2020-04-30 8:55 ` [dts] [PATCH V2 1/3] tests/malicious_driver_event_indication: upload automation yufengmx
2020-04-30 8:55 ` [dts] [PATCH V2 2/3] tests/malicious_driver_event_indication: update test plan yufengmx
2020-04-30 8:55 ` [dts] [PATCH V2 3/3] tests/malicious_driver_event_indication: add " yufengmx
2020-05-06 1:40 ` Mo, YufengX [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=f614d029b5db4d49a4fa4b808646cd74@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).