public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Satish Kharat <satishkh@cisco.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	20260401-enic-sriov-v2-prep-v4-0-d5834b2ef1b9@cisco.com,
	Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH net-next v5 00/10] enic: SR-IOV V2 admin channel and MBOX protocol
Date: Thu, 23 Apr 2026 10:39:41 -0700	[thread overview]
Message-ID: <20260423103941.70a56bfa@kernel.org> (raw)
In-Reply-To: <20260423-enic-sriov-v2-admin-channel-v2-v5-0-caa9f504a3dc@cisco.com>

On Thu, 23 Apr 2026 09:28:01 -0700 Satish Kharat wrote:
> This series adds the admin channel infrastructure and mailbox (MBOX)
> protocol needed for V2 SR-IOV support in the enic driver.
> 
> The V2 SR-IOV design uses a direct PF-VF communication channel built on
> dedicated WQ/RQ/CQ hardware resources and an MSI-X interrupt.

## Form letter - net-next-closed

We have already submitted our pull request with net-next material for v7.1,
and therefore net-next is closed for new drivers, features, code refactoring
and optimizations. We are currently accepting bug fixes only.

Please repost when net-next reopens after Apr 27th.

RFC patches sent for review only are obviously welcome at any time.

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
-- 
pw-bot: defer
pv-bot: closed

      parent reply	other threads:[~2026-04-23 17:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 16:28 [PATCH net-next v5 00/10] enic: SR-IOV V2 admin channel and MBOX protocol Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 01/10] enic: verify firmware supports V2 SR-IOV at probe time Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 02/10] enic: add admin channel open and close for SR-IOV Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 03/10] enic: add admin RQ buffer management Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 04/10] enic: add admin CQ service with MSI-X interrupt and NAPI polling Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 05/10] enic: define MBOX message types and header structures Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 06/10] enic: add MBOX core send and receive for admin channel Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 07/10] enic: add MBOX PF handlers for VF register and capability Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 08/10] enic: add MBOX VF handlers for capability, register and link state Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 09/10] enic: wire V2 SR-IOV enable with admin channel and MBOX Satish Kharat
2026-04-23 16:28 ` [PATCH net-next v5 10/10] enic: add V2 VF probe with admin channel and PF registration Satish Kharat
2026-04-23 17:39 ` Jakub Kicinski [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=20260423103941.70a56bfa@kernel.org \
    --to=kuba@kernel.org \
    --cc=20260401-enic-sriov-v2-prep-v4-0-d5834b2ef1b9@cisco.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=leitao@debian.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