From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Fu, Qi" <qi.fu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Fu, Qi" <qi.fu@intel.com>
Subject: Re: [dts] [PATCH V2 02/17]framework/settings: add carlsville to settings
Date: Fri, 30 Aug 2019 02:53:17 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB076D8@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190829114651.53232-1-qi.fu@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of qifu
> Sent: Thursday, August 29, 2019 7:47 PM
> To: dts@dpdk.org
> Cc: Fu, Qi <qi.fu@intel.com>
> Subject: [dts] [PATCH V2 02/17]framework/settings: add carlsville to settings
>
> Add carlsville to NICS and DRIVERS in settings.py.
> Signed-off-by: qifu <qi.fu@intel.com>
> ---
> framework/settings.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/framework/settings.py b/framework/settings.py index
> 4f0368b..fbff7db 100644
> --- a/framework/settings.py
> +++ b/framework/settings.py
> @@ -107,6 +107,7 @@ NICS = {
> 'fastlinq_ql45000_vf': '1077:1664',
> 'fastlinq_ql41000': '1077:8070',
> 'fastlinq_ql41000_vf': '1077:8090',
> + 'carlsville': '8086:15ff',
> }
>
> DRIVERS = {
> @@ -168,6 +169,7 @@ DRIVERS = {
> 'fastlinq_ql41000': 'qede',
> 'fastlinq_ql45000_vf': 'qede',
> 'fastlinq_ql41000_vf': 'qede',
> + 'carlsville': 'i40e',
> }
>
> """
> --
> 2.17.1
next prev parent reply other threads:[~2019-08-30 2:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 11:06 [dts] [PATCH 00/17] enable carlsville qifu
2019-08-19 11:06 ` [dts] [PATCH 01/17] conf/test_case_checklist: add carlsville to checklist qifu
2019-08-29 11:44 ` [dts] [PATCH V2 01/17]conf/test_case_checklist: " qifu
2019-08-30 2:55 ` Tu, Lijuan
2019-08-19 11:06 ` [dts] [PATCH 02/17] framework/settings: add carlsville to settings qifu
2019-08-29 11:46 ` [dts] [PATCH V2 02/17]framework/settings: " qifu
2019-08-30 2:53 ` Tu, Lijuan [this message]
2019-08-19 11:06 ` [dts] [PATCH 03/17] conf/test_case_supportlist: add carlsville to supportlist qifu
2019-08-19 11:06 ` [dts] [PATCH 04/17] tests/TestSuite_dual_vlan: add carlsville to support nic of dual_vlan qifu
2019-08-19 11:06 ` [dts] [PATCH 05/17] tests/TestSuite_fdir: add carlsville to support nic of fdir qifu
2019-08-19 11:06 ` [dts] [PATCH 06/17] tests/TestSuite_fortville_rss_granularity_config: add carlsville to support nic of fortville_rss_granularity_config qifu
2019-08-19 11:06 ` [dts] [PATCH 07/17] tests/TestSuite_generic_filter: add carlsville to support nic of generic_filter qifu
2019-08-19 11:06 ` [dts] [PATCH 08/17] tests/TestSuite_ipgre: add carlsville to support nic of ipgre qifu
2019-08-19 5:05 ` Mo, YufengX
2019-08-19 5:23 ` Fu, Qi
2019-08-19 5:28 ` Mo, YufengX
2019-08-19 5:40 ` Fu, Qi
2019-08-19 18:09 ` [dts] [PATCH V2 08/17]tests/TestSuite_ipgre: " qifu
2019-08-20 11:02 ` [dts] [PATCH V3 " qifu
2019-08-28 10:39 ` Tu, Lijuan
2019-08-19 11:06 ` [dts] [PATCH 09/17] tests/TestSuite_link_status_interrupt: add carlsville to support nic of link_status_interrupt qifu
2019-08-19 11:06 ` [dts] [PATCH 10/17] tests/TestSuite_nvgre: add carlsville to support nic of nvgre qifu
2019-08-19 11:06 ` [dts] [PATCH 11/17] tests/TestSuite_pmdrss_hash: add carlsville to support nic of pmdrss_hash qifu
2019-08-19 11:06 ` [dts] [PATCH 12/17] tests/TestSuite_ptype_mapping: add carlsville to support nic of ptype_mapping qifu
2019-08-19 11:06 ` [dts] [PATCH 13/17] tests/TestSuite_scatter: add carlsville to support nic of scatter qifu
2019-08-19 11:06 ` [dts] [PATCH 14/17] tests/TestSuite_uni_pkt: add carlsville to support nic of uni_pkt qifu
2019-08-19 11:06 ` [dts] [PATCH 15/17] tests/TestSuite_vlan_ethertype_config: add carlsville to support nic of vlan_ethertype_config qifu
2019-08-19 11:06 ` [dts] [PATCH 16/17] tests/TestSuite_vlan: add carlsville to support nic of vlan qifu
2019-08-19 11:06 ` [dts] [PATCH 17/17] tests/TestSuite_vxlan: add carlsville to support nic of vxlan qifu
2019-08-28 10:36 ` [dts] [PATCH 00/17] enable carlsville Tu, Lijuan
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=8CE3E05A3F976642AAB0F4675D0AD20E0BB076D8@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=qi.fu@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).