From: patchwork-bot+netdevbpf@kernel.org
To: Fan Gong <gongfan1@huawei.com>
Cc: zhuyikai1@h-partners.com, netdev@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, andrew+netdev@lunn.ch,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
luosifu@huawei.com, guoxin09@huawei.com, zhoushuai28@huawei.com,
wulike1@huawei.com, shijing34@huawei.com,
zhengjiezhen@h-partners.com
Subject: Re: [PATCH net-next v03 0/9] net: hinic3: PF initialization
Date: Thu, 12 Mar 2026 11:20:22 +0000 [thread overview]
Message-ID: <177331442229.4053740.17049484553716552945.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1773062356.git.zhuyikai1@h-partners.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 10 Mar 2026 09:04:48 +0800 you wrote:
> This is [2/3] part of hinic3 Ethernet driver second submission.
> With this patch hinic3 becomes a complete Ethernet driver with
> pf and vf.
>
> Add cmdq detailed-response interfaces.
> Add dump interfaces for cmdq, aeq, ceq and mailbox.
> Add msg_send_lock for message sending concurrency.
> Add PF device support and chip_present_flag to check cards.
> Add rx vlan offload support.
> Add PF FLR wait and timeout handling.
> Add 5 ethtool ops for information of driver and link.
>
> [...]
Here is the summary with links:
- [net-next,v03,1/9] hinic3: Add command queue detailed-response interfaces
https://git.kernel.org/netdev/net-next/c/15b5be9389be
- [net-next,v03,2/9] hinic3: Add Command Queue/Async Event Queue/Complete Event Queue/Mailbox dump interfaces
https://git.kernel.org/netdev/net-next/c/678c5b3b6b22
- [net-next,v03,3/9] hinic3: Add chip_present_flag checks to prevent errors when card is absent
https://git.kernel.org/netdev/net-next/c/d69ee992fbf6
- [net-next,v03,4/9] hinic3: Add RX VLAN offload support
https://git.kernel.org/netdev/net-next/c/0f746fc5bc77
- [net-next,v03,5/9] hinic3: Add msg_send_lock for message sending concurrecy
https://git.kernel.org/netdev/net-next/c/2a76f900d17d
- [net-next,v03,6/9] hinic3: Add PF device support and function type validation
https://git.kernel.org/netdev/net-next/c/3d36efc28078
- [net-next,v03,7/9] hinic3: Add PF FLR wait and timeout handling
https://git.kernel.org/netdev/net-next/c/33cf53672b6f
- [net-next,v03,8/9] hinic3: Add PF/VF capability parsing and parameter validation
https://git.kernel.org/netdev/net-next/c/330adcedd003
- [net-next,v03,9/9] hinic3: Add ethtool basic ops
https://git.kernel.org/netdev/net-next/c/00608d02ddf0
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:[~2026-03-12 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 1:04 [PATCH net-next v03 0/9] net: hinic3: PF initialization Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 1/9] hinic3: Add command queue detailed-response interfaces Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 2/9] hinic3: Add Command Queue/Async Event Queue/Complete Event Queue/Mailbox dump interfaces Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 3/9] hinic3: Add chip_present_flag checks to prevent errors when card is absent Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 4/9] hinic3: Add RX VLAN offload support Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 5/9] hinic3: Add msg_send_lock for message sending concurrecy Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 6/9] hinic3: Add PF device support and function type validation Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 7/9] hinic3: Add PF FLR wait and timeout handling Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 8/9] hinic3: Add PF/VF capability parsing and parameter validation Fan Gong
2026-03-10 1:04 ` [PATCH net-next v03 9/9] hinic3: Add ethtool basic ops Fan Gong
2026-03-12 11:20 ` 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=177331442229.4053740.17049484553716552945.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gongfan1@huawei.com \
--cc=guoxin09@huawei.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luosifu@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shijing34@huawei.com \
--cc=wulike1@huawei.com \
--cc=zhengjiezhen@h-partners.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.