From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Yash Sharma <ysharma@marvell.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "shshaikh@marvell.com" <shshaikh@marvell.com>,
"psurana@marvell.com" <psurana@marvell.com>,
"srane@marvell.com" <srane@marvell.com>
Subject: Re: [dts] [PATCH 1/1] framework/test_capabilities.py fastlinq adapters doesn't support SCTP checksum offload, adding driver in Dictionary so that test escape SCTP Checksum part but continue to test other Checksum offload.
Date: Wed, 10 Jul 2019 05:22:37 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BADE8B4@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190705135517.6466-1-ysharma@marvell.com>
Applied, thanks
> -----Original Message-----
> From: Yash Sharma [mailto:ysharma@marvell.com]
> Sent: Friday, July 5, 2019 9:55 PM
> To: dts@dpdk.org; Tu, Lijuan <lijuan.tu@intel.com>
> Cc: shshaikh@marvell.com; psurana@marvell.com; srane@marvell.com; yash
> <ysharma@marvell.com>
> Subject: [PATCH 1/1] framework/test_capabilities.py fastlinq adapters
> doesn't support SCTP checksum offload, adding driver in Dictionary so that
> test escape SCTP Checksum part but continue to test other Checksum offload.
>
> From: yash <ysharma@marvell.com>
>
> Signed-off-by: yash <ysharma@marvell.com>
> ---
> framework/test_capabilities.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/framework/test_capabilities.py b/framework/test_capabilities.py
> index 2ad3fae..79a6dee 100644
> --- a/framework/test_capabilities.py
> +++ b/framework/test_capabilities.py
> @@ -3,7 +3,7 @@
> Dict used to skip parts of tests if NIC is known not to support them """
> DRIVER_TEST_LACK_CAPA = {
> - 'sctp_tx_offload' : ['thunder-nicvf', 'fm10k']
> + 'sctp_tx_offload' : ['thunder-nicvf', 'fm10k', 'qede']
> }
>
>
> --
> 1.8.3.1
prev parent reply other threads:[~2019-07-10 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 13:55 Yash Sharma
2019-07-10 5:22 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BADE8B4@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=psurana@marvell.com \
--cc=shshaikh@marvell.com \
--cc=srane@marvell.com \
--cc=ysharma@marvell.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).