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 DC065A0C47; Sun, 25 Jul 2021 11:47:21 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 532CA40DDA; Sun, 25 Jul 2021 11:47:21 +0200 (CEST) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mails.dpdk.org (Postfix) with ESMTP id 7B56E4003F; Sun, 25 Jul 2021 11:47:19 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10055"; a="199283619" X-IronPort-AV: E=Sophos;i="5.84,266,1620716400"; d="scan'208";a="199283619" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Jul 2021 02:47:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.84,266,1620716400"; d="scan'208";a="578826617" Received: from fmsmsx605.amr.corp.intel.com ([10.18.126.85]) by fmsmga001.fm.intel.com with ESMTP; 25 Jul 2021 02:47:17 -0700 Received: from shsmsx604.ccr.corp.intel.com (10.109.6.214) by fmsmsx605.amr.corp.intel.com (10.18.126.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.4; Sun, 25 Jul 2021 02:47:17 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX604.ccr.corp.intel.com (10.109.6.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.10; Sun, 25 Jul 2021 17:47:15 +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.2242.010; Sun, 25 Jul 2021 17:47:15 +0800 From: "Zhang, Qi Z" To: "Xing, Beilei" , "Li, Xiaoyun" , "dev@dpdk.org" , "Wu, Jingjing" CC: "stable@dpdk.org" Thread-Topic: [PATCH] net/iavf: fix tx thresh check issue Thread-Index: AQHXf2yPtka/5VTO6E+EnqsI72Grm6tTdSCw Date: Sun, 25 Jul 2021 09:47:15 +0000 Message-ID: References: <20210722075620.472438-1-xiaoyun.li@intel.com> In-Reply-To: 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] net/iavf: fix tx thresh check issue 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: dev On Behalf Of Xing, Beilei > Sent: Friday, July 23, 2021 10:43 AM > To: Li, Xiaoyun ; dev@dpdk.org; Wu, Jingjing > > Cc: stable@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] net/iavf: fix tx thresh check issue >=20 >=20 >=20 > > -----Original Message----- > > From: Li, Xiaoyun > > Sent: Thursday, July 22, 2021 3:56 PM > > To: dev@dpdk.org; Wu, Jingjing ; Xing, Beilei > > > > Cc: Li, Xiaoyun ; stable@dpdk.org > > Subject: [PATCH] net/iavf: fix tx thresh check issue > > > > Function check_tx_thresh is called with wrong parameter. If the check > > fails, tx_queue_setup should return error not keep going. > > iThis patch fixes above issues. >=20 > Typo: This >=20 > Except that, > Acked-by: Beilei Xing Applied to dpdk-next-net-intel with typo fix Thanks Qi