DPDK patches and discussions
 help / color / mirror / Atom feed
From: oulijun <oulijun@huawei.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>, <linuxarm@openeuler.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH 00/17] bugfixes and small functionality for hns3
Date: Wed, 3 Feb 2021 20:18:42 +0800	[thread overview]
Message-ID: <abc7ee63-6f8a-fa28-93cd-71c9b8666866@huawei.com> (raw)
In-Reply-To: <93627578-c047-c6f9-0922-db47e35ed91f@intel.com>



在 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.
> .
> 

      reply	other threads:[~2021-02-03 12:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  7:46 Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 01/17] net/hns3: support module EEPROM dump Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 02/17] net/hns3: add more registers to dump Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 03/17] net/hns3: implement cleanup for Tx done Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 04/17] net/hns3: add enhance stats function Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 05/17] net/hns3: fix query order of link status and link info Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 06/17] net/hns3: fix link status change from firmware Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 07/17] net/hns3: encapsulate a port shaping interface Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 08/17] net/hns3: support PF on electrical net device Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 09/17] net/hns3: fix RSS indirection table size Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 10/17] net/hns3: constraint TM peak rate Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 11/17] net/hns3: remove MPLS type from supported flow items Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 12/17] net/hns3: fix stats flip overflow Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 13/17] net/hns3: replace all atomic type with C11 atomic builtins Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 14/17] net/hns3: fix FD rule residue in hardware when malloc fail Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 15/17] net/hns3: fix cmdq cleared during firmware process Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 16/17] net/hns3: fix VF reset after MBX failed Lijun Ou
2021-02-03  7:46 ` [dpdk-dev] [PATCH 17/17] net/hns3: add check for max pkt length of Rx Lijun Ou
2021-02-03  9:24 ` [dpdk-dev] [PATCH 00/17] bugfixes and small functionality for hns3 Ferruh Yigit
2021-02-03 11:05   ` oulijun
2021-02-03 11:46     ` Ferruh Yigit
2021-02-03 12:18       ` oulijun [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=abc7ee63-6f8a-fa28-93cd-71c9b8666866@huawei.com \
    --to=oulijun@huawei.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=linuxarm@openeuler.org \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).