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 8B3DEA0A0E; Wed, 3 Feb 2021 12:46:34 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 24A46240501; Wed, 3 Feb 2021 12:46:34 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mails.dpdk.org (Postfix) with ESMTP id 96D762404FD for ; Wed, 3 Feb 2021 12:46:32 +0100 (CET) IronPort-SDR: lSr/Dx4cswR0NzXqytNRYPEE8BWqzTx9afLqcpFWaXOBPCCsko1XXhWWfLoRI3CP2G6UyZPWLx +WmSMl6EGXIw== X-IronPort-AV: E=McAfee;i="6000,8403,9883"; a="180253199" X-IronPort-AV: E=Sophos;i="5.79,398,1602572400"; d="scan'208";a="180253199" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2021 03:46:31 -0800 IronPort-SDR: klk7J4JoYjbkLKzF3UBC+cD10iJ0ZEn+4xVx/uZRA1DnGnfNESl8ov2x3bgEIZM515kTfNVdxZ Ro4eGyTsa+yw== X-IronPort-AV: E=Sophos;i="5.79,398,1602572400"; d="scan'208";a="433377080" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.245.26]) ([10.213.245.26]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2021 03:46:30 -0800 To: oulijun Cc: dev@dpdk.org, linuxarm@openeuler.org, Thomas Monjalon , David Marchand References: <1612338382-3253-1-git-send-email-oulijun@huawei.com> From: Ferruh Yigit Message-ID: <93627578-c047-c6f9-0922-db47e35ed91f@intel.com> Date: Wed, 3 Feb 2021 11:46:26 +0000 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH 00/17] bugfixes and small functionality for hns3 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" On 2/3/2021 11:05 AM, oulijun wrote: > > > 在 2021/2/3 17:24, Ferruh Yigit 写道: >> On 2/3/2021 7:46 AM, Lijun Ou wrote: >>> This patch series add some bugfixes and some small >>> functions. In order to fix some bugfixes, we had to >>> do some code rework, for example patch[13/17]. >>> >>> Chengchang Tang (6): >>>    net/hns3: support module EEPROM dump >>>    net/hns3: add more registers to dump >>>    net/hns3: fix stats flip overflow >>>    net/hns3: replace all atomic type with C11 atomic builtins >>>    net/hns3: fix cmdq cleared during firmware process >>>    net/hns3: fix VF reset after MBX failed >>> >>> Chengwen Feng (4): >>>    net/hns3: implement cleanup for Tx done >>>    net/hns3: constraint TM peak rate >>>    net/hns3: remove MPLS type from supported flow items >>>    net/hns3: fix FD rule residue in hardware when malloc fail >>> >>> Huisong Li (5): >>>    net/hns3: fix query order of link status and link info >>>    net/hns3: fix link status change from firmware >>>    net/hns3: encapsulate a port shaping interface >>>    net/hns3: support PF on electrical net device >>>    net/hns3: add check for max pkt length of Rx >>> >>> Lijun Ou (1): >>>    net/hns3: fix RSS indirection table size >>> >>> Min Hu (Connor) (1): >>>    net/hns3: add enhance stats function >>> >> >> Hi Lijun, >> >> Is this for next release or current release? >> We are a day away from the -rc3 and a week (almost) away from the actual >> release, it is safer to limit the patches to fixes at this stage. >> >> If above set is for this release, can you please make a new version to have >> only fixes, and leave the new supports and refactoring and not important fixes >> to next release? >> > Yes, I've been aware of our expectations and requirements of each rc. Therefore, > we have selected some new support items that have been developed and tested in > the roadmap and hope to integrate them in the rc3. Some key bug fixes are > expected to be fixed in the current version as soon as possible. Still not sure about getting new small functionality in the last day of the -rc3, what do you think get the fixes and push the new functionality to next release? Technically new features should be sent _before_ the proposal deadline, December 20, and we are more flexible for the drivers but there should be a deadline eventually.