From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhao, HaiyangX" <haiyangx.zhao@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V2 0/5] framework: add a proposal of recognizing pkgs
Date: Fri, 19 Mar 2021 08:49:40 +0000 [thread overview]
Message-ID: <ad95ae29368e4c7d8756869a71912175@intel.com> (raw)
In-Reply-To: <20210318092215.27270-1-haiyangx.zhao@intel.com>
> v2:
> fix exception when get pkg info.
> v1:
>
> Now there are os default/comms/wireless pkgs for CVL NIC, and they support
> different protocals. Some suite like l2tp_esp_coverage are partly support these
> pkgs, we replace the pkg in suite to support the case in the past, but this may
> occur exception and the result may not be we want, so we provide a new
> proposal by adding a decorate above test case to check if the pkg support
> current case, and do not replace pkg in suite.
>
> This patch set is the proposal of framework modification.
>
> Haiyang Zhao (5):
> framework/exception: add new exception VerifySkip
> framework/test_case: handle the VerifySkip exception and add some
> functions
> nics/net_device: add attribute pkg and get method
> framework/dut: get nic package in dut prerequisites
> tests: add nic and pkg check for rss_gtpu
Applied, thanks
prev parent reply other threads:[~2021-03-19 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 9:22 Haiyang Zhao
2021-03-18 9:22 ` [dts] [PATCH V2 1/5] framework/exception: add new exception VerifySkip Haiyang Zhao
2021-03-18 9:22 ` [dts] [PATCH V2 2/5] framework/test_case: handle the VerifySkip exception and add some functions Haiyang Zhao
2021-03-18 9:22 ` [dts] [PATCH V2 3/5] nics/net_device: add attribute pkg and get method Haiyang Zhao
2021-03-18 9:22 ` [dts] [PATCH V2 4/5] framework/dut: get nic package in dut prerequisites Haiyang Zhao
2021-03-18 9:22 ` [dts] [PATCH V2 5/5] tests: add nic and pkg check for rss_gtpu Haiyang Zhao
2021-03-19 8:49 ` 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=ad95ae29368e4c7d8756869a71912175@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=haiyangx.zhao@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).