patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Huisong Li <lihuisong@huawei.com>
To: <stable@dpdk.org>, <ktraynor@redhat.com>
Cc: <liuyonglong@huawei.com>, <lihuisong@huawei.com>
Subject: [PATCH 21.11 0/4] backport some bugfix for hns3
Date: Thu, 23 Nov 2023 16:05:25 +0800	[thread overview]
Message-ID: <20231123080529.15216-1-lihuisong@huawei.com> (raw)

The patch [2/4] and [3/4] depend on patch [1/4]. So have to backport it.

Huisong Li (4):
  net/hns3: extract common function to obtain revision ID
  net/hns3: fix setting DCB capability
  net/hns3: fix LRO offload to report
  net/hns3: fix crash for NEON and SVE

 drivers/net/hns3/hns3_cmd.c          | 40 ++++++++++++++++++++++++++++
 drivers/net/hns3/hns3_cmd.h          |  1 +
 drivers/net/hns3/hns3_common.c       | 27 +++++++++++++++++--
 drivers/net/hns3/hns3_common.h       |  1 +
 drivers/net/hns3/hns3_ethdev.c       | 31 ++++-----------------
 drivers/net/hns3/hns3_ethdev.h       |  1 +
 drivers/net/hns3/hns3_ethdev_vf.c    | 23 ++++------------
 drivers/net/hns3/hns3_rxtx.c         |  5 +++-
 drivers/net/hns3/hns3_rxtx_vec.c     |  5 ++++
 drivers/net/hns3/hns3_rxtx_vec_sve.c |  5 ++++
 10 files changed, 92 insertions(+), 47 deletions(-)

-- 
2.33.0


             reply	other threads:[~2023-11-23  8:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  8:05 Huisong Li [this message]
2023-11-23  8:05 ` [PATCH 21.11 1/4] net/hns3: extract common function to obtain revision ID Huisong Li
2023-11-23  8:05 ` [PATCH 21.11 2/4] net/hns3: fix setting DCB capability Huisong Li
2023-11-23  8:05 ` [PATCH 21.11 3/4] net/hns3: fix LRO offload to report Huisong Li
2023-11-23  8:05 ` [PATCH 21.11 4/4] net/hns3: fix crash for NEON and SVE Huisong Li
2023-11-23 10:52 ` [PATCH 21.11 0/4] backport some bugfix for hns3 Kevin Traynor

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=20231123080529.15216-1-lihuisong@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=ktraynor@redhat.com \
    --cc=liuyonglong@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).