From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dts-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id 12427A00E6
	for <public@inbox.dpdk.org>; Thu, 18 Apr 2019 12:33:03 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id B65F01B93F;
	Thu, 18 Apr 2019 12:33:02 +0200 (CEST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210])
 by dpdk.org (Postfix) with ESMTP id 5066F1B939
 for <dts@dpdk.org>; Thu, 18 Apr 2019 12:33:02 +0200 (CEST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.108])
 by Forcepoint Email with ESMTP id A51506C9F25432CE1330;
 Thu, 18 Apr 2019 11:33:01 +0100 (IST)
Received: from LHREML503-MBS.china.huawei.com ([10.201.109.56]) by
 lhreml702-cah.china.huawei.com ([10.201.108.43]) with mapi id 14.03.0415.000; 
 Thu, 18 Apr 2019 11:32:57 +0100
From: Rami Rosen <rami.rosen@huawei.com>
To: "Lin, Xueqin" <xueqin.lin@intel.com>, "Xu, Yanjie" <yanjie.xu@intel.com>, 
 "dts@dpdk.org" <dts@dpdk.org>
CC: "Xu, Yanjie" <yanjie.xu@intel.com>
Thread-Topic: [dts] [PATCH] dynamic add hardware requirement
Thread-Index: AQHU9b15EvQd2bPYdUWDXAlSBY7e06ZBgnKAgAA1rdA=
Date: Thu, 18 Apr 2019 10:32:56 +0000
Message-ID: <5151E1D101B7B04382075E3B0EF69373EC1C5F@lhreml503-mbs>
References: <1555595465-174360-1-git-send-email-yanjie.xu@intel.com>
 <0D300480287911409D9FF92C1FA2A3355B4D6BD1@SHSMSX104.ccr.corp.intel.com>
In-Reply-To: <0D300480287911409D9FF92C1FA2A3355B4D6BD1@SHSMSX104.ccr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.210.168.243]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [dts] [PATCH] dynamic add hardware requirement
X-BeenThere: dts@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: test suite reviews and discussions <dts.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dts>,
 <mailto:dts-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dts/>
List-Post: <mailto:dts@dpdk.org>
List-Help: <mailto:dts-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dts>,
 <mailto:dts-request@dpdk.org?subject=subscribe>
Errors-To: dts-bounces@dpdk.org
Sender: "dts" <dts-bounces@dpdk.org>

Hi,

>[Xueqin] The scope is too large, in /dpdk/drivers/net path, there are so m=
any driver types, we may >test this suite on e1000, ixgbe, i40e, not try al=
l especially not try on some not-intel NICs.
>"Any type NIC" is not make sense. =20


+1 on this.

Actually, as of now, DTS supports nics from four vendors: Intel, Cavium Net=
works, Mellanox and Huawei (see framework/setting.py)

Regards,
Rami=20