From: Yogesh Jangra <yogesh.jangra@intel.com>
To: dts@dpdk.org
Cc: cristian.dumitrescu@intel.com, kamalakannan.r@intel.com,
harshad.suresh.narayane@intel.com, yogesh.jangra@intel.com
Subject: [PATCH 0/2] added test case for validate instruction
Date: Tue, 29 Nov 2022 06:02:39 +0000 [thread overview]
Message-ID: <20221129060241.901035-1-yogesh.jangra@intel.com> (raw)
Added the test case for validate instruction.
Yogesh Jangra (2):
dep/pipeline: added dependencies for validate_002 test case
tests/pipeline: added test case for validate instruction
dep/pipeline/validate_002/ethdev.io | 27 ++++++
dep/pipeline/validate_002/pcap_files/in_1.txt | 16 ++++
.../validate_002/pcap_files/out_1.txt | 12 +++
dep/pipeline/validate_002/readme.md | 12 +++
dep/pipeline/validate_002/table.txt | 1 +
dep/pipeline/validate_002/validate_002.cli | 22 +++++
dep/pipeline/validate_002/validate_002.spec | 82 +++++++++++++++++++
tests/TestSuite_pipeline.py | 13 +++
8 files changed, 185 insertions(+)
create mode 100644 dep/pipeline/validate_002/ethdev.io
create mode 100644 dep/pipeline/validate_002/pcap_files/in_1.txt
create mode 100644 dep/pipeline/validate_002/pcap_files/out_1.txt
create mode 100644 dep/pipeline/validate_002/readme.md
create mode 100644 dep/pipeline/validate_002/table.txt
create mode 100644 dep/pipeline/validate_002/validate_002.cli
create mode 100644 dep/pipeline/validate_002/validate_002.spec
--
2.25.1
next reply other threads:[~2022-11-29 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 6:02 Yogesh Jangra [this message]
2022-11-29 6:02 ` [PATCH 1/2] dep/pipeline: added dependencies for validate_002 test case Yogesh Jangra
2022-11-29 6:02 ` [PATCH 2/2] tests/pipeline: added test case for validate instruction Yogesh Jangra
2022-12-13 7:01 ` [PATCH 0/2] " Tu, Lijuan
2022-12-13 7:16 ` Jangra, Yogesh
2022-12-13 7:56 ` Tu, Lijuan
2022-12-13 12:09 ` Jangra, Yogesh
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=20221129060241.901035-1-yogesh.jangra@intel.com \
--to=yogesh.jangra@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dts@dpdk.org \
--cc=harshad.suresh.narayane@intel.com \
--cc=kamalakannan.r@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).