From: patchwork-bot+netdevbpf@kernel.org
To: Fan Gong <gongfan1@huawei.com>
Cc: zhuyikai1@h-partners.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, andrew+netdev@lunn.ch,
linux-doc@vger.kernel.org, corbet@lwn.net, helgaas@kernel.org,
luosifu@huawei.com, guoxin09@huawei.com,
shenchenyang1@hisilicon.com, zhoushuai28@huawei.com,
wulike1@huawei.com, shijing34@huawei.com,
fuguiming@h-partners.com, meny.yossefi@huawei.com,
gur.stavi@huawei.com, lee@trager.us, mpe@ellerman.id.au,
vadim.fedorenko@linux.dev, sumang@marvell.com,
przemyslaw.kitszel@intel.com, jdamato@fastly.com,
christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH net-next v14 0/8] net: hinic3: Add a driver for Huawei 3rd gen NIC - management interfaces
Date: Sat, 23 Aug 2025 00:30:25 +0000 [thread overview]
Message-ID: <175590902523.2040371.14804037397876219083.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1755673097.git.zhuyikai1@h-partners.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 Aug 2025 17:31:17 +0800 you wrote:
> This is the 2/3 patch of the patch-set described below.
>
> The patch-set contains driver for Huawei's 3rd generation HiNIC
> Ethernet device that will be available in the future.
>
> This is an SRIOV device, designed for data centers.
> Initially, the driver only supports VFs.
>
> [...]
Here is the summary with links:
- [net-next,v14,1/8] hinic3: Async Event Queue interfaces
https://git.kernel.org/netdev/net-next/c/a4511307be86
- [net-next,v14,2/8] hinic3: Complete Event Queue interfaces
https://git.kernel.org/netdev/net-next/c/c4bbfd9b0d32
- [net-next,v14,3/8] hinic3: Command Queue framework
https://git.kernel.org/netdev/net-next/c/db03a1ced61c
- [net-next,v14,4/8] hinic3: Command Queue interfaces
https://git.kernel.org/netdev/net-next/c/16a6fce06757
- [net-next,v14,5/8] hinic3: TX & RX Queue coalesce interfaces
https://git.kernel.org/netdev/net-next/c/bef7c33c6754
- [net-next,v14,6/8] hinic3: Mailbox framework
https://git.kernel.org/netdev/net-next/c/2742e06e2d42
- [net-next,v14,7/8] hinic3: Mailbox management interfaces
https://git.kernel.org/netdev/net-next/c/a8255ea56aee
- [net-next,v14,8/8] hinic3: Interrupt request configuration
https://git.kernel.org/netdev/net-next/c/a5a90346bb12
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-23 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 9:31 Fan Gong
2025-08-20 9:31 ` [PATCH net-next v14 1/8] hinic3: Async Event Queue interfaces Fan Gong
2025-08-20 9:31 ` [PATCH net-next v14 2/8] hinic3: Complete " Fan Gong
2025-08-20 9:31 ` [PATCH net-next v14 3/8] hinic3: Command Queue framework Fan Gong
2025-08-20 9:31 ` [PATCH net-next v14 4/8] hinic3: Command Queue interfaces Fan Gong
2025-08-20 9:31 ` [PATCH net-next v14 5/8] hinic3: TX & RX Queue coalesce interfaces Fan Gong
2025-08-20 9:31 ` [PATCH net-next v14 6/8] hinic3: Mailbox framework Fan Gong
2025-08-20 9:31 ` [PATCH net-next v14 7/8] hinic3: Mailbox management interfaces Fan Gong
2025-08-20 9:31 ` [PATCH net-next v14 8/8] hinic3: Interrupt request configuration Fan Gong
2025-08-23 0:30 ` patchwork-bot+netdevbpf [this message]
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=175590902523.2040371.14804037397876219083.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=christophe.jaillet@wanadoo.fr \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fuguiming@h-partners.com \
--cc=gongfan1@huawei.com \
--cc=guoxin09@huawei.com \
--cc=gur.stavi@huawei.com \
--cc=helgaas@kernel.org \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luosifu@huawei.com \
--cc=meny.yossefi@huawei.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shenchenyang1@hisilicon.com \
--cc=shijing34@huawei.com \
--cc=sumang@marvell.com \
--cc=vadim.fedorenko@linux.dev \
--cc=wulike1@huawei.com \
--cc=zhoushuai28@huawei.com \
--cc=zhuyikai1@h-partners.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®