From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Jangra, Yogesh" <yogesh.jangra@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "P, Venkata Suresh Kumar" <venkata.suresh.kumar.p@intel.com>,
"Suresh Narayane, Harshad" <harshad.suresh.narayane@intel.com>,
"Jangra, Yogesh" <yogesh.jangra@intel.com>
Subject: RE: [PATCH 2/2] tests/pipeline: add support for annotations in pipeline test suite
Date: Tue, 25 Jan 2022 02:42:42 +0000 [thread overview]
Message-ID: <46cd698a29e14705846f9b4b2fa20f0f@intel.com> (raw)
In-Reply-To: <1641866138-122679-3-git-send-email-yogesh.jangra@intel.com>
> -----Original Message-----
> From: Yogesh Jangra <yogesh.jangra@intel.com>
> Sent: 2022年1月11日 9:56
> To: dts@dpdk.org
> Cc: P, Venkata Suresh Kumar <venkata.suresh.kumar.p@intel.com>; Suresh
> Narayane, Harshad <harshad.suresh.narayane@intel.com>; Jangra, Yogesh
> <yogesh.jangra@intel.com>
> Subject: [PATCH 2/2] tests/pipeline: add support for annotations in pipeline test
> suite
>
> This patch has P4 action annotation support, port type and updates for
> mempool size to add support to run the suite on virtual machine.
>
> Signed-off-by: Yogesh Jangra <yogesh.jangra@intel.com>
> Signed-off-by: Harshad Suresh Narayane <harshad.suresh.narayane@intel.com>
> Tested-by: Venkata Suresh Kumar P <venkata.suresh.kumar.p@intel.com>
Applied the series.
prev parent reply other threads:[~2022-01-25 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 1:55 [PATCH 0/2] add pipeline annotation and VM support test coverage Yogesh Jangra
2022-01-11 1:55 ` [PATCH 1/2] dep: add support for annotations for pipeline test suite dependencies Yogesh Jangra
2022-01-11 1:55 ` [PATCH 2/2] tests/pipeline: add support for annotations in pipeline test suite Yogesh Jangra
2022-01-25 2:42 ` 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=46cd698a29e14705846f9b4b2fa20f0f@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=harshad.suresh.narayane@intel.com \
--cc=venkata.suresh.kumar.p@intel.com \
--cc=yogesh.jangra@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).