patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Wei Hu (Xavier)" <xavier.huwei@huawei.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, <dev@dpdk.org>
Cc: <xavier_huwei@163.com>, <xavier.huwei@tom.com>,
	<linuxarm@huawei.com>, <forest.zhouchang@huawei.com>,
	<stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2 0/4] some fixes for hns3 PMD driver
Date: Sat, 26 Oct 2019 09:56:11 +0800	[thread overview]
Message-ID: <b3eb229f-2435-017e-551d-ce25e497011e@huawei.com> (raw)
In-Reply-To: <23d1d0c7-f1c4-e17b-e01a-2a11d6fd46c3@huawei.com>

Hi,  Ferruh Yigit

    Can this series of fixes be added to dpdk version 19.11?
    Thanks.

    Regards
Xavier

On 2019/10/26 9:03, Wei Hu (Xavier) wrote:
>
> On 2019/10/25 23:07, Ferruh Yigit wrote:
>> On 10/25/2019 1:37 PM, Wei Hu (Xavier) wrote:
>>> This series adds some fixes for hns3 ethernet pmd driver.
>>>
>>> v1 -> v2:
>>> 	1. Address some comments from Ferruh Yigit as belows:
>>> 	   https://inbox.dpdk.org/dev/31868759-1900-2aad-4e38-0ae8fe52647a@intel.com
>>> 	   https://inbox.dpdk.org/dev/e5d5bd99-663d-5661-dfda-312c762b2887@intel.com
>>> 	   https://inbox.dpdk.org/dev/b4a32414-b941-c820-1706-f8ad41175764@intel.com
>>>
>>> Chunsong Feng (1):
>>>   net/hns3: fix FLR reset failure
>>>
>>> Hao Chen (1):
>>>   net/hns3: fix the statistics problems about Tx/Rx functions
>>>
>>> Hongbo Zheng (1):
>>>   net/hns3: fix the return value when firmware timeout
>>>
>>> Wei Hu (Xavier) (1):
>>>   net/hns3: fix lack of Rx RSS hash in ol flags
>> Series applied to dpdk-next-net/master, thanks.
>>
> Thanks a lot.
>
>
> _______________________________________________
> Linuxarm mailing list
> Linuxarm@huawei.com
> http://hulk.huawei.com/mailman/listinfo/linuxarm
>
> .
>



           reply	other threads:[~2019-10-26  2:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <23d1d0c7-f1c4-e17b-e01a-2a11d6fd46c3@huawei.com>]

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=b3eb229f-2435-017e-551d-ce25e497011e@huawei.com \
    --to=xavier.huwei@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=forest.zhouchang@huawei.com \
    --cc=linuxarm@huawei.com \
    --cc=stable@dpdk.org \
    --cc=xavier.huwei@tom.com \
    --cc=xavier_huwei@163.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).