public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@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>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sesidhar Baddela <sebaddel@cisco.com>,
	Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH net-next v6 00/10] enic: SR-IOV V2 admin channel and MBOX protocol
Date: Wed, 6 May 2026 17:19:38 +0100	[thread overview]
Message-ID: <20260506161938.GS15617@horms.kernel.org> (raw)
In-Reply-To: <20260503-enic-sriov-v2-admin-channel-v2-v6-0-0af4fbc2d86d@cisco.com>

On Sun, May 03, 2026 at 04:22:37AM -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.
> 
> Firmware capability and admin channel infrastructure (patches 1-4):
>   - Probe-time firmware feature check for V2 SR-IOV support
>   - Admin channel open/close, RQ buffer management, CQ service
>     with MSI-X interrupt and NAPI polling
> 
> MBOX protocol and VF enable (patches 5-10):
>   - MBOX message types, core send/receive, PF and VF handlers
>   - V2 SR-IOV enable wiring with admin channel setup
>   - V2 VF probe with admin channel and PF registration
> 
> Signed-off-by: Satish Kharat <satishkh@cisco.com>

Hi Satish,

There is are AI-generated reviews of this patch available at both
https://netdev-ai.bots.linux.dev/sashiko/ and https://sashiko.dev/
And it seems to me that some of the issues raised there do warrant
investigation. I'd appreciate it if you could do so with
a view to addressing any issues that are not pre-existing in v7.

...

      parent reply	other threads:[~2026-05-06 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 11:22 [PATCH net-next v6 00/10] enic: SR-IOV V2 admin channel and MBOX protocol Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 01/10] enic: verify firmware supports V2 SR-IOV at probe time Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 02/10] enic: add admin channel open and close for SR-IOV Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 03/10] enic: add admin RQ buffer management Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 04/10] enic: add admin CQ service with MSI-X interrupt and NAPI polling Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 05/10] enic: define MBOX message types and header structures Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 06/10] enic: add MBOX core send and receive for admin channel Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 07/10] enic: add MBOX PF handlers for VF register and capability Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 08/10] enic: add MBOX VF handlers for capability, register and link state Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 09/10] enic: wire V2 SR-IOV enable with admin channel and MBOX Satish Kharat
2026-05-03 11:22 ` [PATCH net-next v6 10/10] enic: add V2 VF probe with admin channel and PF registration Satish Kharat
2026-05-06 16:19 ` Simon Horman [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=20260506161938.GS15617@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=satishkh@cisco.com \
    --cc=sebaddel@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