From: Salil Mehta <salil.mehta@huawei.com>
To: <dledford@redhat.com>
Cc: <salil.mehta@huawei.com>, <yisen.zhuang@huawei.com>,
<xavier.huwei@huawei.com>, <oulijun@huawei.com>,
<mehta.salil.lnk@gmail.com>, <linux-rdma@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>
Subject: [PATCH V2 for-next 0/8] Bug Fixes and Code Improvement in HNS driver
Date: Thu, 29 Sep 2016 18:09:08 +0100 [thread overview]
Message-ID: <20160929170916.631972-1-salil.mehta@huawei.com> (raw)
This patch-set introduces fix to some Bugs, potential problems
and code improvements identified during internal review and
testing of Hisilicon Network Subsystem driver.
Submit Change
V1->V2: This addresses the feedbacks provided by David Miller
and Doug Ledford
Daode Huang (6):
net: hns: bug fix about setting coalsecs-usecs to 0
net: hns: add fini_process for v2 napi process
net: hns: delete repeat read fbd num after while
net: hns: fix the bug of forwarding table
net: hns: bug fix about broadcast/multicast packets
net: hns: delete redundant broadcast packet filter process
Kejian Yan (1):
net: hns: fix port not available after testing loopback
lipeng (1):
net: hns: fix port unavailable after hnae_reserve_buffer_map fail
drivers/net/ethernet/hisilicon/hns/hns_ae_adapt.c | 11 +-
drivers/net/ethernet/hisilicon/hns/hns_dsaf_mac.c | 13 ++-
drivers/net/ethernet/hisilicon/hns/hns_dsaf_mac.h | 2 +
drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c | 10 --
drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.h | 1 -
drivers/net/ethernet/hisilicon/hns/hns_dsaf_rcb.c | 16 +++
drivers/net/ethernet/hisilicon/hns/hns_dsaf_reg.h | 4 +
drivers/net/ethernet/hisilicon/hns/hns_enet.c | 107 +++++++++++++-------
drivers/net/ethernet/hisilicon/hns/hns_ethtool.c | 7 ++
9 files changed, 118 insertions(+), 53 deletions(-)
--
1.7.9.5
next reply other threads:[~2016-09-29 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 17:09 Salil Mehta [this message]
2016-09-29 17:09 ` [PATCH V2 for-next 1/8] net: hns: fix port unavailable after hnae_reserve_buffer_map fail Salil Mehta
2016-09-29 17:09 ` [PATCH V2 for-next 2/8] net: hns: bug fix about setting coalsecs-usecs to 0 Salil Mehta
2016-09-29 17:09 ` [PATCH V2 for-next 3/8] net: hns: add fini_process for v2 napi process Salil Mehta
2016-09-29 17:09 ` [PATCH V2 for-next 4/8] net: hns: delete repeat read fbd num after while Salil Mehta
2016-09-29 17:09 ` [PATCH V2 for-next 5/8] net: hns: fix port not available after testing loopback Salil Mehta
2016-09-29 17:09 ` [PATCH V2 for-next 6/8] net: hns: fix the bug of forwarding table Salil Mehta
2016-09-29 17:09 ` [PATCH V2 for-next 7/8] net: hns: bug fix about broadcast/multicast packets Salil Mehta
2016-09-29 17:09 ` [PATCH V2 for-next 8/8] net: hns: delete redundant broadcast packet filter process Salil Mehta
2016-09-30 5:33 ` [PATCH V2 for-next 0/8] Bug Fixes and Code Improvement in HNS driver David Miller
2016-09-30 13:38 ` Doug Ledford
2016-10-13 11:26 ` Salil Mehta
2016-10-13 11:57 ` Doug Ledford
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=20160929170916.631972-1-salil.mehta@huawei.com \
--to=salil.mehta@huawei.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mehta.salil.lnk@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oulijun@huawei.com \
--cc=xavier.huwei@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®