From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4FF61A052A; Tue, 26 Jan 2021 04:25:24 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3892A1411DE; Tue, 26 Jan 2021 04:25:24 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id A8EB91411DB for ; Tue, 26 Jan 2021 04:25:22 +0100 (CET) IronPort-SDR: uHMCU79UHx1xDg1gBNaxPRh24FgW1k+9Bivh1hoo6Kib9KOleDLFx+w/TzGkPpz64YPTRrWRU/ ik0aPhHCbZow== X-IronPort-AV: E=McAfee;i="6000,8403,9875"; a="159019389" X-IronPort-AV: E=Sophos;i="5.79,375,1602572400"; d="scan'208";a="159019389" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Jan 2021 19:25:21 -0800 IronPort-SDR: PmhWX6XsJ5c0EA1JHuQUy1BI44g4jNJbxAfAurok9hTFWzIF0XSJCyaQDHTTNOXq6L9Hxv4Q8r uFNkWFqAI/Dg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,375,1602572400"; d="scan'208";a="572798614" Received: from fmsmsx603.amr.corp.intel.com ([10.18.126.83]) by orsmga005.jf.intel.com with ESMTP; 25 Jan 2021 19:25:21 -0800 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) by fmsmsx603.amr.corp.intel.com (10.18.126.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 25 Jan 2021 19:25:20 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX603.ccr.corp.intel.com (10.109.6.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 26 Jan 2021 11:25:19 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.1713.004; Tue, 26 Jan 2021 11:25:19 +0800 From: "Zhang, Qi Z" To: "Wang, Haiyue" , "dev@dpdk.org" CC: "Yang, Qiming" , "Wu, Jingjing" , "Xing, Beilei" Thread-Topic: [PATCH v1] net/iavf: adjust the VLAN failure handling Thread-Index: AQHW8xGsqh7uiKT6qUii2keD43mugKo5P3CA Date: Tue, 26 Jan 2021 03:25:18 +0000 Message-ID: References: <20210125114421.56152-1-haiyue.wang@intel.com> In-Reply-To: <20210125114421.56152-1-haiyue.wang@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.5.1.3 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v1] net/iavf: adjust the VLAN failure handling X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" > -----Original Message----- > From: Wang, Haiyue > Sent: Monday, January 25, 2021 7:44 PM > To: dev@dpdk.org > Cc: Yang, Qiming ; Zhang, Qi Z > ; Wang, Haiyue ; Wu, > Jingjing ; Xing, Beilei > Subject: [PATCH v1] net/iavf: adjust the VLAN failure handling >=20 > Change the fatal returning to print the error message only, so that the V= F > device can continue to be configured. >=20 > Fixes: 1c301e8c3cff ("net/iavf: support new VLAN capabilities") >=20 > Signed-off-by: Haiyue Wang > --- Acked-by: Qi Zhang Applied to dpdk-next-net-intel. Thanks Qi