DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: oulijun <oulijun@huawei.com>
Cc: dev <dev@dpdk.org>, Linuxarm <linuxarm@huawei.com>
Subject: Re: [dpdk-dev] [PATCH 0/4] hns3 fixes
Date: Fri, 20 Nov 2020 15:38:24 +0000	[thread overview]
Message-ID: <241b964a-2ca3-7386-4115-77859a429145@intel.com> (raw)
In-Reply-To: <20626160478b4b16b15b8995e7c6c826@huawei.com>

On 11/20/2020 2:58 PM, oulijun wrote:

< Moved to the bottom, please do not top post >

>> 
>> --------------------------------------------------------------------------------
>> 
>> 欧丽军
>> Mobile:+86-18899774289 <tel:+86-18899774289>
>> Email:oulijun@huawei.com <mailto:oulijun@huawei.com>
>> 
>> 
>> *发件人: *Ferruh Yigit<ferruh.yigit@intel.com <mailto:ferruh.yigit@intel.com>>
>> *收件人: *oulijun<oulijun@huawei.com <mailto:oulijun@huawei.com>>
>> *抄送: *dev<dev@dpdk.org <mailto:dev@dpdk.org>>;Linuxarm<linuxarm@huawei.com 
>> <mailto:linuxarm@huawei.com>>
>> *主题: *Re: [PATCH 0/4] hns3 fixes
>> *时间: *2020-11-20 22:39:13
>> 
>> On 11/20/2020 11:27 AM, Lijun Ou wrote:
>>> Here series are fixes for hns3 PMD driver.
>>> 
>>> Chengchang Tang (1):
>>>    net/hns3: fix unused queues with not disabled
>>> 
>>> Huisong Li (1):
>>>    net/hns3: fix segment fault with the multi-TC
>>> 
>>> Lijun Ou (1):
>>>    net/hns3: adjust printing MAC addresses in log
>>> 
>>> Min Hu (Conor) (1):
>>>    net/hns3: fix FEC state query
>>> 
>> 
>> Hi Lijun,
>> 
>> How critical these fixes are?
>> We have -rc5 today, and release this Wednesday, so these will be last minute
>> fixes, if these are not critical I suggest postponing to next release and fixes
>> can be backported from there to LTS.
 >
 > Hi,Ferruh
 > the first and second patch are critical.
 >

OK, lets target first two patches for this release and defer rest.

  reply	other threads:[~2020-11-20 15:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 11:27 Lijun Ou
2020-11-20 11:27 ` [dpdk-dev] [PATCH 1/4] net/hns3: fix segment fault with the multi-TC Lijun Ou
2020-11-20 11:27 ` [dpdk-dev] [PATCH 2/4] net/hns3: fix unused queues with not disabled Lijun Ou
2020-11-20 11:27 ` [dpdk-dev] [PATCH 3/4] net/hns3: adjust printing MAC addresses in log Lijun Ou
2020-11-20 14:25   ` Ferruh Yigit
2020-12-07 14:52     ` oulijun
2020-12-10 11:54       ` oulijun
2020-11-20 11:27 ` [dpdk-dev] [PATCH 4/4] net/hns3: fix FEC state query Lijun Ou
2020-11-20 14:33   ` Ferruh Yigit
2020-11-20 14:35     ` Ferruh Yigit
2020-12-02 12:42       ` Min Hu (Connor)
2020-12-07 14:50     ` oulijun
2020-11-20 14:38 ` [dpdk-dev] [PATCH 0/4] hns3 fixes Ferruh Yigit
2020-11-20 14:58   ` oulijun
2020-11-20 15:38     ` Ferruh Yigit [this message]
2020-11-20 17:53       ` Ferruh Yigit
2020-12-07 14:54       ` oulijun
2020-12-07 16:17         ` Ferruh Yigit
2020-12-10 12:48 ` [dpdk-dev] [PATCH V2 0/2] " Lijun Ou
2020-12-10 12:48   ` [dpdk-dev] [PATCH V2 1/2] net/hns3: adjust printing MAC addresses in log Lijun Ou
2020-12-10 12:48   ` [dpdk-dev] [PATCH V2 2/2] net/hns3: fix FEC state query Lijun Ou
2020-12-10 16:30   ` [dpdk-dev] [PATCH V2 0/2] hns3 fixes Ferruh Yigit
2020-12-11  1:44     ` oulijun

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=241b964a-2ca3-7386-4115-77859a429145@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=linuxarm@huawei.com \
    --cc=oulijun@huawei.com \
    /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).