patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: "lihuisong@huawei.com" <lihuisong@huawei.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "fengchengwen@huawei.com" <fengchengwen@huawei.com>
Subject: Re: [PATCH V1 0/2][20.11] net/hns3: backport two patches to 20.11.4
Date: Sat, 13 Nov 2021 09:02:52 +0000	[thread overview]
Message-ID: <6a4c61c29d4984000cba4c11731764f74670a8d5.camel@nvidia.com> (raw)
In-Reply-To: <20211113083412.20894-1-lihuisong@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

Hi Huisong,

Thanks for backporting.

Subject "20.11" is missing, append to avoid it mixed with other LTS.

On Sat, 2021-11-13 at 16:34 +0800, Huisong Li wrote:

Backport two patches to stable release 20.11.4


Chengwen Feng (1):

  net/hns3: fix interrupt vector freeing


Huisong Li (1):

  net/hns3: fix residual MAC after setting default MAC


 drivers/net/hns3/hns3_ethdev.c    | 38 +++++++++----------------------

 drivers/net/hns3/hns3_ethdev.h    |  1 -

 drivers/net/hns3/hns3_ethdev_vf.c |  2 +-

 3 files changed, 12 insertions(+), 29 deletions(-)



[-- Attachment #2: Type: text/html, Size: 1116 bytes --]

  parent reply	other threads:[~2021-11-13  9:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13  8:34 [PATCH V1 0/2] " Huisong Li
2021-11-13  8:34 ` [PATCH V1 1/2] net/hns3: fix residual MAC after setting default MAC Huisong Li
2021-11-13  8:34 ` [PATCH V1 2/2] net/hns3: fix interrupt vector freeing Huisong Li
2021-11-13  9:02 ` Xueming(Steven) Li [this message]
2021-11-13  9:17 ` [PATCH 20.11 V2 0/2] net/hns3: backport two patches to 20.11.4 Huisong Li
2021-11-13  9:17   ` [PATCH 20.11 V2 1/2] net/hns3: fix residual MAC after setting default MAC Huisong Li
2021-11-27 13:55     ` Xueming(Steven) Li
2021-12-06  6:11       ` lihuisong (C)
2021-11-13  9:17   ` [PATCH 20.11 V2 2/2] net/hns3: fix interrupt vector freeing Huisong Li
2021-11-27 13:56     ` Xueming(Steven) Li

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=6a4c61c29d4984000cba4c11731764f74670a8d5.camel@nvidia.com \
    --to=xuemingl@nvidia.com \
    --cc=fengchengwen@huawei.com \
    --cc=lihuisong@huawei.com \
    --cc=stable@dpdk.org \
    /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).