mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: netdev-bot+sashiko@kernel.org
To: illusion.wang@nebula-matrix.com
Cc: dimon.zhao@nebula-matrix.com, alvin.wang@nebula-matrix.com,
	sam.chen@nebula-matrix.com, netdev@vger.kernel.org,
	kuba@kernel.org, andrew+netdev@lunn.ch, pabeni@redhat.com,
	edumazet@google.com, horms@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v32 net-next 6/8] net/nebula-matrix: dispatch: implement channel RPC framework and serialize hardware ops
Date: Sun, 25 Oct 2026 09:24:26 +0000	[thread overview]
Message-ID: <179292026679.3134.13737137805222935440@kernel.org> (raw)
In-Reply-To: <20261021062113.2158-7-illusion.wang@nebula-matrix.com>

Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.

Low priority / nit picks for your consideration:

- [Low] Baseline decision: false (resolved later in the series, retained
  only because requires_validation=true).

--

net/nebula-matrix: dispatch: implement channel RPC framework and serialize hardware ops

This patch adds mailbox RPC requests and responders for cfg_msix_map,
destroy_msix_map, set_mailbox_irq, get_vsi_id and get_eth_id. Each op
resolves to a local resource call when has_ctrl is set, or to a channel
RPC to the management PF when has_net is set. The five responders are
registered with the channel layer from nbl_disp_setup_msg().

> nbl_disp_remove() documents why the five responders, which are owned by
> the channel layer, need no explicit unregistration.

[Severity: Low]
Is this paragraph accurate for this patch? The patch does not change
nbl_disp_remove() in nbl_dispatch.c, and at this commit it still reads:

void nbl_disp_remove(struct nbl_adapter *adapter)
{
	/* Dispatch structures are allocated via devm */
}

There is nothing there about the responders that nbl_disp_setup_msg()
registers.

The kernel-doc for struct nbl_dispatch_ops in nbl_def_dispatch.h also sends
readers to nbl_disp_remove() for that explanation:

 * structures are devm-allocated in nbl_disp_init(), and nbl_disp_remove()
 * only documents why no explicit teardown is needed.

The full comment arrives in the next patch in the series, "net/nebula-matrix:
add common/ctrl dev init/remove operation". It explains the teardown order
cancel_work_sync -> nbl_chan_teardown_queue -> nbl_chan_remove_common ->
nbl_chan_remove_msg_handler.

Could this paragraph be dropped from this commit message, or the comment
moved into this patch, so each commit matches its own message?

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261021062113.2158-1-illusion.wang%40nebula-matrix.com

  reply	other threads:[~2026-10-25  9:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  6:20 [PATCH v32 net-next 0/8] nbl driver for Nebulamatrix NICs illusion.wang
2026-10-21  6:21 ` [PATCH v32 net-next 1/8] net/nebula-matrix: add channel layer illusion.wang
2026-10-25  9:24   ` netdev-bot+sashiko
2026-10-21  6:21 ` [PATCH v32 net-next 2/8] net/nebula-matrix: add common resource implementation illusion.wang
2026-10-21  6:21 ` [PATCH v32 net-next 3/8] net/nebula-matrix: add intr " illusion.wang
2026-10-25  9:24   ` netdev-bot+sashiko
2026-10-21  6:21 ` [PATCH v32 net-next 4/8] net/nebula-matrix: add chip-wide hardware init/deinit implementation illusion.wang
2026-10-25  9:24   ` netdev-bot+sashiko
2026-10-21  6:21 ` [PATCH v32 net-next 5/8] net/nebula-matrix: dispatch: add control-level routing core infrastructure illusion.wang
2026-10-21  6:21 ` [PATCH v32 net-next 6/8] net/nebula-matrix: dispatch: implement channel RPC framework and serialize hardware ops illusion.wang
2026-10-25  9:24   ` netdev-bot+sashiko [this message]
2026-10-21  6:21 ` [PATCH v32 net-next 7/8] net/nebula-matrix: add common/ctrl dev init/remove operation illusion.wang
2026-10-25  9:24   ` netdev-bot+sashiko
2026-10-21  6:21 ` [PATCH v32 net-next 8/8] net/nebula-matrix: add common dev start/stop operation illusion.wang
2026-10-25  9:24   ` netdev-bot+sashiko
2026-10-21 21:34 ` [PATCH v32 net-next 0/8] nbl driver for Nebulamatrix NICs Jakub Kicinski

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=179292026679.3134.13737137805222935440@kernel.org \
    --to=netdev-bot+sashiko@kernel.org \
    --cc=alvin.wang@nebula-matrix.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=dimon.zhao@nebula-matrix.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=illusion.wang@nebula-matrix.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sam.chen@nebula-matrix.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®