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 468A9A0531; Tue, 4 Feb 2020 04:24:24 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 919231C014; Tue, 4 Feb 2020 04:24:23 +0100 (CET) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 6D1221C012; Tue, 4 Feb 2020 04:24:21 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Feb 2020 19:24:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,398,1574150400"; d="scan'208";a="403657072" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.117.17]) by orsmga005.jf.intel.com with ESMTP; 03 Feb 2020 19:24:18 -0800 Date: Tue, 4 Feb 2020 11:23:20 +0800 From: Ye Xiaolong To: Kevin Traynor Cc: "Xing, Beilei" , "Zhang, Qi Z" , "dev@dpdk.org" , "stable@dpdk.org" , Luca Boccassi Message-ID: <20200204032320.GN54838@intel.com> References: <20191202074935.97629-1-xiaolong.ye@intel.com> <20200113023949.26718-1-xiaolong.ye@intel.com> <94479800C636CB44BD422CB454846E013CEC8CCD@SHSMSX101.ccr.corp.intel.com> <008b5b10198142fe92d08cd9f5bf1b33@intel.com> <5f6b078d-23c5-0970-2d82-b512da8fb752@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5f6b078d-23c5-0970-2d82-b512da8fb752@redhat.com> User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [PATCH v4 00/36] update for i40e base code 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" Hi, Kevin On 02/03, Kevin Traynor wrote: >On 13/01/2020 05:59, Ye, Xiaolong wrote: [snip] >>> -----Original Message----- >Hi Xiaolong/Beilei/Qi Z, > >Some of these patches are tagged to go to 'S'table and are 'F'ixes, >while others are also fixes for older releases but not tagged to go to >stable. > >No issue with not backporting patches (in fact i would prefer not if >some doubts), but want to check if the stable tag was missed by accident? > >Also, note that Fw listed is v6.01 for 18.11, (v7.00 for 19.11) so >changes would need to be compatible with that. Yes, some of the stable tags were missed deliberately since the new base code update is for FW 7.1/7.2, it's not guaranteed to be compatible with old FW. > >20.02 8f33cbcfa S F net/i40e/base: fix buffer address (16.04) >20.02 4b3da9415 S F net/i40e/base: fix error message (1.7.0) >20.02 1da546c39 - F net/i40e/base: fix missing link modes (17.08) >20.02 79bfe7808 S F net/i40e/base: fix Tx descriptors number (1.7.0) >20.02 50126939c - F net/i40e/base: fix retrying logic (18.02) >20.02 b330a1c5c - F net/i40e/base: fix display of FEC settings (17.08) >20.02 03ef7d47f - F net/i40e/base: add new link speed constants (17.08) > I would suggest we only backport below obvious fixes to stable releases. 20.02 8f33cbcfa S F net/i40e/base: fix buffer address (16.04) 20.02 4b3da9415 S F net/i40e/base: fix error message (1.7.0) 20.02 79bfe7808 S F net/i40e/base: fix Tx descriptors number (1.7.0) 20.02 50126939c - F net/i40e/base: fix retrying logic (18.02) Thanks, Xiaolong >Please confirm on patches above missing stable tag. For time being I >will only consider ones with stable tag. > >thanks, >Kevin. >