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 V2 net-next 0/6] net: hns3: updates for -next
Date: Mon, 09 May 2022 13:40:14 +0000 [thread overview]
Message-ID: <165210361417.30657.1832076685595767481.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220509075532.32166-1-huangguangbin2@huawei.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 9 May 2022 15:55:26 +0800 you wrote:
> This series includes some updates for the HNS3 ethernet driver.
>
> Change logs:
> V1 -> V2:
> - Fix some sparse warnings of patch 3# and 4#.
> - Add patch #6 to fix sparse warnings of incorrect type of argument.
>
> [...]
Here is the summary with links:
- [V2,net-next,1/6] net: hns3: fix access null pointer issue when set tx-buf-size as 0
https://git.kernel.org/netdev/net-next/c/a4fe9b6db6f9
- [V2,net-next,2/6] net: hns3: remove the affinity settings of vector0
https://git.kernel.org/netdev/net-next/c/bbed70241204
- [V2,net-next,3/6] net: hns3: add byte order conversion for PF to VF mailbox message
https://git.kernel.org/netdev/net-next/c/767975e582c5
- [V2,net-next,4/6] net: hns3: add byte order conversion for VF to PF mailbox message
https://git.kernel.org/netdev/net-next/c/416eedb60361
- [V2,net-next,5/6] net: hns3: add query vf ring and vector map relation
https://git.kernel.org/netdev/net-next/c/a1aed456e326
- [V2,net-next,6/6] net: hns3: fix incorrect type of argument in declaration of function hclge_comm_get_rss_indir_tbl
https://git.kernel.org/netdev/net-next/c/443edfd6d43d
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-05-09 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 7:55 [PATCH V2 net-next 0/6] net: hns3: updates for -next Guangbin Huang
2022-05-09 7:55 ` [PATCH V2 net-next 1/6] net: hns3: fix access null pointer issue when set tx-buf-size as 0 Guangbin Huang
2022-05-09 7:55 ` [PATCH V2 net-next 2/6] net: hns3: remove the affinity settings of vector0 Guangbin Huang
2022-05-09 7:55 ` [PATCH V2 net-next 3/6] net: hns3: add byte order conversion for PF to VF mailbox message Guangbin Huang
2022-05-09 7:55 ` [PATCH V2 net-next 4/6] net: hns3: add byte order conversion for VF to PF " Guangbin Huang
2022-05-09 7:55 ` [PATCH V2 net-next 5/6] net: hns3: add query vf ring and vector map relation Guangbin Huang
2022-05-09 7:55 ` [PATCH V2 net-next 6/6] net: hns3: fix incorrect type of argument in declaration of function hclge_comm_get_rss_indir_tbl Guangbin Huang
2022-05-09 13:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-16 9:33 [PATCH V2 net-next 0/6] net: hns3: updates for -next Huazhong Tan
2020-09-16 20:44 ` Saeed Mahameed
2020-09-17 23:14 ` 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=165210361417.30657.1832076685595767481.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