From: patchwork-bot+netdevbpf@kernel.org
To: Guangbin Huang <huangguangbin2@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lipeng321@huawei.com,
chenhao288@hisilicon.com
Subject: Re: [PATCH net 0/6] net: hns3: add some fixes for -net
Date: Sat, 26 Mar 2022 16:20:11 +0000 [thread overview]
Message-ID: <164831161125.22978.5795474197257933400.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220326095105.54075-1-huangguangbin2@huawei.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Sat, 26 Mar 2022 17:50:59 +0800 you wrote:
> This series adds some fixes for the HNS3 ethernet driver.
>
> Guangbin Huang (1):
> net: hns3: fix phy can not link up when autoneg off and reset
>
> Hao Chen (4):
> net: hns3: fix ethtool tx copybreak buf size indicating not aligned
> issue
> net: hns3: add max order judgement for tx spare buffer
> net: hns3: add netdev reset check for hns3_set_tunable()
> net: hns3: add NULL pointer check for hns3_set/get_ringparam()
>
> [...]
Here is the summary with links:
- [net,1/6] net: hns3: fix ethtool tx copybreak buf size indicating not aligned issue
https://git.kernel.org/netdev/net/c/877837211802
- [net,2/6] net: hns3: add max order judgement for tx spare buffer
https://git.kernel.org/netdev/net/c/a89cbb16995b
- [net,3/6] net: hns3: clean residual vf config after disable sriov
https://git.kernel.org/netdev/net/c/671cb8cbb9c9
- [net,4/6] net: hns3: add netdev reset check for hns3_set_tunable()
https://git.kernel.org/netdev/net/c/f5cd60169f98
- [net,5/6] net: hns3: add NULL pointer check for hns3_set/get_ringparam()
https://git.kernel.org/netdev/net/c/4d07c5936c25
- [net,6/6] net: hns3: fix phy can not link up when autoneg off and reset
https://git.kernel.org/netdev/net/c/ad0ecaef6a2c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-03-26 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 9:50 Guangbin Huang
2022-03-26 9:51 ` [PATCH net 1/6] net: hns3: fix ethtool tx copybreak buf size indicating not aligned issue Guangbin Huang
2022-03-26 9:51 ` [PATCH net 2/6] net: hns3: add max order judgement for tx spare buffer Guangbin Huang
2022-03-26 9:51 ` [PATCH net 3/6] net: hns3: clean residual vf config after disable sriov Guangbin Huang
2022-03-26 9:51 ` [PATCH net 4/6] net: hns3: add netdev reset check for hns3_set_tunable() Guangbin Huang
2022-03-26 9:51 ` [PATCH net 5/6] net: hns3: add NULL pointer check for hns3_set/get_ringparam() Guangbin Huang
2022-03-26 9:51 ` [PATCH net 6/6] net: hns3: fix phy can not link up when autoneg off and reset Guangbin Huang
2022-03-26 16:20 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-11 12:25 [PATCH net 0/6] net: hns3: add some fixes for -net Guangbin Huang
2022-06-13 11:00 ` patchwork-bot+netdevbpf
2022-04-24 12:57 Guangbin Huang
2022-04-25 9:50 ` patchwork-bot+netdevbpf
2021-09-15 13:52 Guangbin Huang
2021-09-13 13:08 Guangbin Huang
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=164831161125.22978.5795474197257933400.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chenhao288@hisilicon.com \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.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
Powered by JetHome