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 8D9A6A0A0E; Wed, 3 Feb 2021 13:18:46 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 772C2240533; Wed, 3 Feb 2021 13:18:46 +0100 (CET) Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [45.249.212.190]) by mails.dpdk.org (Postfix) with ESMTP id E904C240532 for ; Wed, 3 Feb 2021 13:18:44 +0100 (CET) Received: from DGGEMS413-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4DW0zh4cLxzlFDh; Wed, 3 Feb 2021 20:17:04 +0800 (CST) Received: from [10.67.103.119] (10.67.103.119) by DGGEMS413-HUB.china.huawei.com (10.3.19.213) with Microsoft SMTP Server id 14.3.498.0; Wed, 3 Feb 2021 20:18:42 +0800 To: Ferruh Yigit CC: , , Thomas Monjalon , David Marchand References: <1612338382-3253-1-git-send-email-oulijun@huawei.com> <93627578-c047-c6f9-0922-db47e35ed91f@intel.com> From: oulijun Message-ID: Date: Wed, 3 Feb 2021 20:18:42 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <93627578-c047-c6f9-0922-db47e35ed91f@intel.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.103.119] X-CFilter-Loop: Reflected 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" 在 2021/2/3 19:46, Ferruh Yigit 写道: > 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? > Thanks， I see. > 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. > . >