From: patchwork-bot+netdevbpf@kernel.org
To: Jijie Shao <shaojijie@huawei.com>
Cc: yisen.zhuang@huawei.com, salil.mehta@huawei.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shenjian15@huawei.com, wangjie125@huawei.com,
liuyonglong@huawei.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 net 0/7] There are some bugfix for the HNS3 ethernet driver
Date: Mon, 13 Nov 2023 09:38:28 +0000 [thread overview]
Message-ID: <169986830857.24663.16656088717775298434.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231110093713.1895949-1-shaojijie@huawei.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 10 Nov 2023 17:37:06 +0800 you wrote:
> There are some bugfix for the HNS3 ethernet driver
>
> ---
> ChangeLog:
> v1 -> v2:
> - net: hns3: fix add VLAN fail issue, net: hns3: fix VF reset fail issue
> are modified suggested by Paolo
> v1: https://lore.kernel.org/all/20231028025917.314305-1-shaojijie@huawei.com/
>
> [...]
Here is the summary with links:
- [V2,net,1/7] net: hns3: fix add VLAN fail issue
https://git.kernel.org/netdev/net/c/472a2ff63efb
- [V2,net,2/7] net: hns3: add barrier in vf mailbox reply process
https://git.kernel.org/netdev/net/c/ac92c0a9a060
- [V2,net,3/7] net: hns3: fix incorrect capability bit display for copper port
https://git.kernel.org/netdev/net/c/75b247b57d8b
- [V2,net,4/7] net: hns3: fix out-of-bounds access may occur when coalesce info is read via debugfs
https://git.kernel.org/netdev/net/c/53aba458f238
- [V2,net,5/7] net: hns3: fix variable may not initialized problem in hns3_init_mac_addr()
https://git.kernel.org/netdev/net/c/dbd2f3b20c6a
- [V2,net,6/7] net: hns3: fix VF reset fail issue
https://git.kernel.org/netdev/net/c/65e98bb56fa3
- [V2,net,7/7] net: hns3: fix VF wrong speed and duplex issue
https://git.kernel.org/netdev/net/c/dff655e82faf
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:[~2023-11-13 9:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 9:37 Jijie Shao
2023-11-10 9:37 ` [PATCH V2 net 1/7] net: hns3: fix add VLAN fail issue Jijie Shao
2023-11-10 9:37 ` [PATCH V2 net 2/7] net: hns3: add barrier in vf mailbox reply process Jijie Shao
2023-11-10 9:37 ` [PATCH V2 net 3/7] net: hns3: fix incorrect capability bit display for copper port Jijie Shao
2023-11-10 9:37 ` [PATCH V2 net 4/7] net: hns3: fix out-of-bounds access may occur when coalesce info is read via debugfs Jijie Shao
2023-11-10 9:37 ` [PATCH V2 net 5/7] net: hns3: fix variable may not initialized problem in hns3_init_mac_addr() Jijie Shao
2023-11-10 9:37 ` [PATCH V2 net 6/7] net: hns3: fix VF reset fail issue Jijie Shao
2023-11-10 9:37 ` [PATCH V2 net 7/7] net: hns3: fix VF wrong speed and duplex issue Jijie Shao
2023-11-13 9:38 ` patchwork-bot+netdevbpf [this message]
2024-04-26 10:00 [PATCH V2 net 0/7] There are some bugfix for the HNS3 ethernet driver Jijie Shao
2024-12-16 13:23 Jijie Shao
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=169986830857.24663.16656088717775298434.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=wangjie125@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
Powered by JetHome