From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3B0A7A09E8; Tue, 8 Dec 2020 16:53:37 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1B75672D9; Tue, 8 Dec 2020 16:53:36 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 3F35AA3 for ; Tue, 8 Dec 2020 16:53:33 +0100 (CET) IronPort-SDR: y8EJ9P8Y2E2v4VWBf9Y2q1N8Dfy/QHB86J/XjwkpzZamgsxpGzYT8RRd+AHMPQwcHp53nXM5I2 cIujCDaAKY0Q== X-IronPort-AV: E=McAfee;i="6000,8403,9828"; a="173149487" X-IronPort-AV: E=Sophos;i="5.78,402,1599548400"; d="scan'208";a="173149487" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Dec 2020 07:53:32 -0800 IronPort-SDR: YMS9drXcC53vRj8ErnHomN1G14BnzoLQc7IwmpAPRx/3s14DwrCmh3FJ4TAD1xOOKNPXCx5URR oR1R7yXy4iog== X-IronPort-AV: E=Sophos;i="5.78,402,1599548400"; d="scan'208";a="317857541" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.231.143]) ([10.213.231.143]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Dec 2020 07:53:31 -0800 To: Stephen Hemminger References: <20201123221918.20825-1-stephen@networkplumber.org> <20201123221918.20825-3-stephen@networkplumber.org> From: Ferruh Yigit Cc: dev@dpdk.org Message-ID: Date: Tue, 8 Dec 2020 15:53:26 +0000 MIME-Version: 1.0 In-Reply-To: <20201123221918.20825-3-stephen@networkplumber.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH 2/2] net/netvsc: fix ethdev get_supported_ptypes X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 11/23/2020 10:19 PM, Stephen Hemminger wrote: > When doing rte_eth_dev_get_supported_ptypes on netvsc device > the values reported are incorrect if VF is not present. > > If no VF is present the device uses rte_net_get_ptype() > which can return a wide range of values. Use the same table > as TAP device in that case. > > Signed-off-by: Stephen Hemminger Which commit is fixed, can you please add Fixes tag?