From: Huazhong Tan <tanhuazhong@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <salil.mehta@huawei.com>,
<yisen.zhuang@huawei.com>, <huangdaode@huawei.com>,
<linuxarm@openeuler.org>, Huazhong Tan <tanhuazhong@huawei.com>
Subject: [PATCH V2 net-next 0/6] net: hns3: updates for -nex
Date: Fri, 5 Feb 2021 16:32:43 +0800 [thread overview]
Message-ID: <1612513969-9278-1-git-send-email-tanhuazhong@huawei.com> (raw)
This series adds some code optimizations and compatibility
handlings for the HNS3 ethernet driver.
change log:
V2: refactor #2 as Jukub Kicinski reported and remove the part
about RSS size which will not be different in different hw.
updates netdev->max_mtu as well in #4 reported by Jakub Kicinski.
previous version:
V1: https://patchwork.kernel.org/project/netdevbpf/cover/1612269593-18691-1-git-send-email-tanhuazhong@huawei.com/
Guangbin Huang (3):
net: hns3: RSS indirection table use device specification
net: hns3: debugfs add max tm rate specification print
net: hns3: replace macro of max qset number with specification
GuoJia Liao (1):
net: hns3: optimize the code when update the tc info
Jian Shen (1):
net: hns3: add api capability bits for firmware
Yufeng Mo (1):
net: hns3: add support for obtaining the maximum frame size
drivers/net/ethernet/hisilicon/hns3/hnae3.h | 5 +-
drivers/net/ethernet/hisilicon/hns3/hns3_debugfs.c | 3 ++
drivers/net/ethernet/hisilicon/hns3/hns3_enet.c | 3 +-
drivers/net/ethernet/hisilicon/hns3/hns3_enet.h | 5 +-
drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.c | 6 +--
.../net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.c | 10 ++++
.../net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.h | 9 +++-
.../ethernet/hisilicon/hns3/hns3pf/hclge_debugfs.c | 8 ++-
.../ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 57 +++++++++++++++-------
.../ethernet/hisilicon/hns3/hns3pf/hclge_main.h | 8 +--
.../net/ethernet/hisilicon/hns3/hns3pf/hclge_tm.c | 15 ++++--
.../ethernet/hisilicon/hns3/hns3vf/hclgevf_cmd.c | 10 ++++
.../ethernet/hisilicon/hns3/hns3vf/hclgevf_cmd.h | 9 +++-
.../ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c | 47 ++++++++++++------
.../ethernet/hisilicon/hns3/hns3vf/hclgevf_main.h | 8 +--
15 files changed, 140 insertions(+), 63 deletions(-)
--
2.7.4
next reply other threads:[~2021-02-05 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 8:32 Huazhong Tan [this message]
2021-02-05 8:32 ` [PATCH V2 net-next 1/6] net: hns3: add api capability bits for firmware Huazhong Tan
2021-02-05 8:32 ` [PATCH V2 net-next 2/6] net: hns3: RSS indirection table use device specification Huazhong Tan
2021-02-05 8:32 ` [PATCH V2 net-next 3/6] net: hns3: optimize the code when update the tc info Huazhong Tan
2021-02-05 8:32 ` [PATCH V2 net-next 4/6] net: hns3: add support for obtaining the maximum frame size Huazhong Tan
2021-02-05 8:32 ` [PATCH V2 net-next 5/6] net: hns3: debugfs add max tm rate specification print Huazhong Tan
2021-02-05 8:32 ` [PATCH V2 net-next 6/6] net: hns3: replace macro of max qset number with specification Huazhong Tan
2021-02-06 22:40 ` [PATCH V2 net-next 0/6] net: hns3: updates for -nex patchwork-bot+netdevbpf
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=1612513969-9278-1-git-send-email-tanhuazhong@huawei.com \
--to=tanhuazhong@huawei.com \
--cc=davem@davemloft.net \
--cc=huangdaode@huawei.com \
--cc=kuba@kernel.org \
--cc=linuxarm@openeuler.org \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.