From: Salil Mehta <salil.mehta@huawei.com>
To: <davem@davemloft.net>
Cc: <salil.mehta@huawei.com>, <yisen.zhuang@huawei.com>,
<lipeng321@huawei.com>, <mehta.salil@opnsrc.net>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>
Subject: [PATCH net-next 0/5] net: hns3: Add vf mtu support
Date: Sun, 18 Nov 2018 03:19:09 +0000 [thread overview]
Message-ID: <20181118031914.23892-1-salil.mehta@huawei.com> (raw)
This patchset adds vf mtu support to HNS3 driver.
Yunsheng Lin (5):
net: hns3: Support two vlan header when setting mtu
net: hns3: Refactor mac mtu setting related functions
net: hns3: Add vport alive state checking support
net: hns3: Add mtu setting support for vf
net: hns3: up/down netdev in hclge module when setting mtu
.../net/ethernet/hisilicon/hns3/hclge_mbx.h | 3 +
drivers/net/ethernet/hisilicon/hns3/hnae3.h | 6 +
.../net/ethernet/hisilicon/hns3/hns3_enet.c | 39 +++--
.../net/ethernet/hisilicon/hns3/hns3_enet.h | 5 +-
.../hisilicon/hns3/hns3pf/hclge_main.c | 148 ++++++++++++++----
.../hisilicon/hns3/hns3pf/hclge_main.h | 16 +-
.../hisilicon/hns3/hns3pf/hclge_mbx.c | 49 ++++++
.../hisilicon/hns3/hns3vf/hclgevf_main.c | 76 ++++++++-
.../hisilicon/hns3/hns3vf/hclgevf_main.h | 2 +
9 files changed, 295 insertions(+), 49 deletions(-)
--
2.17.1
next reply other threads:[~2018-11-18 3:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 3:19 Salil Mehta [this message]
2018-11-18 3:19 ` [PATCH net-next 1/5] net: hns3: Support two vlan header when setting mtu Salil Mehta
2018-11-18 3:19 ` [PATCH net-next 2/5] net: hns3: Refactor mac mtu setting related functions Salil Mehta
2018-11-18 3:19 ` [PATCH net-next 3/5] net: hns3: Add vport alive state checking support Salil Mehta
2018-11-18 3:19 ` [PATCH net-next 4/5] net: hns3: Add mtu setting support for vf Salil Mehta
2018-11-18 3:19 ` [PATCH net-next 5/5] net: hns3: up/down netdev in hclge module when setting mtu Salil Mehta
2018-11-18 5:57 ` [PATCH net-next 0/5] net: hns3: Add vf mtu support David Miller
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=20181118031914.23892-1-salil.mehta@huawei.com \
--to=salil.mehta@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=mehta.salil@opnsrc.net \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox