From: patchwork-bot+netdevbpf@kernel.org
To: Satish Kharat <satishkh@cisco.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/6] enic: SR-IOV V2 preparatory infrastructure
Date: Fri, 03 Apr 2026 01:10:31 +0000 [thread overview]
Message-ID: <177517863103.685228.4446344909237183027.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260401-enic-sriov-v2-prep-v4-0-d5834b2ef1b9@cisco.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 01 Apr 2026 08:31:10 -0700 you wrote:
> This is the first of four series adding SR-IOV V2 support to the enic
> driver for Cisco VIC 14xx/15xx adapters.
>
> The existing V1 SR-IOV implementation has VFs that interact directly
> with the VIC firmware, leaving the PF driver with no visibility or
> control over VF behavior. V2 introduces a PF-mediated model where VFs
> communicate with the PF through a mailbox over a dedicated admin
> channel. This brings enic in line with the standard Linux SR-IOV
> model, enabling full PF management of VFs via ip link (MAC, VLAN,
> link state, spoofchk, trust, and per-VF statistics).
>
> [...]
Here is the summary with links:
- [net-next,v4,1/6] enic: extend resource discovery for SR-IOV admin channel
https://git.kernel.org/netdev/net-next/c/74fb32ed733c
- [net-next,v4,2/6] enic: add V2 SR-IOV VF device ID
https://git.kernel.org/netdev/net-next/c/803a1b020279
- [net-next,v4,3/6] enic: detect SR-IOV VF type from PCI capability
https://git.kernel.org/netdev/net-next/c/56a4d7a86586
- [net-next,v4,4/6] enic: make enic_dev_enable/disable ref-counted
https://git.kernel.org/netdev/net-next/c/0266ecb59d52
- [net-next,v4,5/6] enic: add type-aware alloc for WQ, RQ, CQ and INTR resources
https://git.kernel.org/netdev/net-next/c/730ce15d4497
- [net-next,v4,6/6] enic: detect admin channel resources for SR-IOV
https://git.kernel.org/netdev/net-next/c/4368f5fab419
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-04-03 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 15:31 [PATCH net-next v4 0/6] enic: SR-IOV V2 preparatory infrastructure Satish Kharat via B4 Relay
2026-04-01 15:31 ` [PATCH net-next v4 1/6] enic: extend resource discovery for SR-IOV admin channel Satish Kharat via B4 Relay
2026-04-01 15:31 ` [PATCH net-next v4 2/6] enic: add V2 SR-IOV VF device ID Satish Kharat via B4 Relay
2026-04-01 15:31 ` [PATCH net-next v4 3/6] enic: detect SR-IOV VF type from PCI capability Satish Kharat via B4 Relay
2026-04-01 15:31 ` [PATCH net-next v4 4/6] enic: make enic_dev_enable/disable ref-counted Satish Kharat via B4 Relay
2026-04-01 15:31 ` [PATCH net-next v4 5/6] enic: add type-aware alloc for WQ, RQ, CQ and INTR resources Satish Kharat via B4 Relay
2026-04-01 15:31 ` [PATCH net-next v4 6/6] enic: detect admin channel resources for SR-IOV Satish Kharat via B4 Relay
2026-04-03 1:10 ` 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=177517863103.685228.4446344909237183027.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=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=satishkh@cisco.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