From: Luo bin <luobin9@huawei.com>
To: <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<luoxianjun@huawei.com>, <luobin9@huawei.com>,
<yin.yinshi@huawei.com>, <cloud.wangxiaoyun@huawei.com>
Subject: [PATCH net 0/5] hinic: BugFixes
Date: Fri, 20 Mar 2020 23:13:15 +0000 [thread overview]
Message-ID: <20200320231320.1001-1-luobin9@huawei.com> (raw)
Fix a number of bugs which have been present since the first commit.
The bugs fixed in these patchs are hardly exposed unless given
very specific conditions.
Luo bin (5):
hinic: fix a bug of waitting for IO stopped
hinic: fix the bug of clearing event queue
hinic: fix out-of-order excution in arm cpu
hinic: fix wrong para of wait_for_completion_timeout
hinic: fix wrong value of MIN_SKB_LEN
.../net/ethernet/huawei/hinic/hinic_hw_cmdq.c | 5 +-
.../net/ethernet/huawei/hinic/hinic_hw_dev.c | 51 +------------------
.../net/ethernet/huawei/hinic/hinic_hw_eqs.c | 26 +++++++---
.../net/ethernet/huawei/hinic/hinic_hw_mgmt.c | 5 +-
drivers/net/ethernet/huawei/hinic/hinic_rx.c | 3 ++
drivers/net/ethernet/huawei/hinic/hinic_tx.c | 4 +-
6 files changed, 34 insertions(+), 60 deletions(-)
--
2.17.1
next reply other threads:[~2020-03-21 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 23:13 Luo bin [this message]
2020-03-20 23:13 ` [PATCH net 1/5] hinic: fix a bug of waitting for IO stopped Luo bin
2020-03-20 23:13 ` [PATCH net 2/5] hinic: fix the bug of clearing event queue Luo bin
2020-03-20 23:13 ` [PATCH net 3/5] hinic: fix out-of-order excution in arm cpu Luo bin
2020-03-20 23:13 ` [PATCH net 4/5] hinic: fix wrong para of wait_for_completion_timeout Luo bin
2020-03-20 23:13 ` [PATCH net 5/5] hinic: fix wrong value of MIN_SKB_LEN Luo bin
2020-03-22 2:44 ` [PATCH net 0/5] hinic: BugFixes 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=20200320231320.1001-1-luobin9@huawei.com \
--to=luobin9@huawei.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luoxianjun@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=yin.yinshi@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;
as well as URLs for NNTP newsgroup(s).