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,
andrew+netdev@lunn.ch, corbet@lwn.net, kuba@kernel.org,
horms@kernel.org, linux-doc@vger.kernel.org, pabeni@redhat.com,
vadim.fedorenko@linux.dev, lukas.bulwahn@redhat.com,
edumazet@google.com, enelsonmoore@gmail.com,
skhan@linuxfoundation.org, hkallweit1@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [v26,net-next,01/10] net/nebula-matrix: add minimum nbl build framework
Date: Thu, 03 Sep 2026 17:18:32 +0000 [thread overview]
Message-ID: <178845591249.3394541.8367854604654150435@kernel.org> (raw)
In-Reply-To: <20260831021408.2325-2-illusion.wang@nebula-matrix.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue(s) to consider:
Critical: 0 · High: 0 · Medium: 0 · Low: 1
- [Low] The documentation file added by this patch,
Documentation/networking/device_drivers/ethernet/nebula-matrix/nbl.rst…
--
net/nebula-matrix: add minimum nbl build framework
This adds the Kconfig/Makefile/MAINTAINERS entries for a new
drivers/net/ethernet/nebula-matrix/ vendor directory, a driver
documentation file, and a PCI driver skeleton (nbl_main.c) whose probe
and remove callbacks are stubs.
> diff --git a/Documentation/networking/device_drivers/ethernet/nebula-matrix/nbl.rst b/Documentation/networking/device_drivers/ethernet/nebula-matrix/nbl.rst
> new file mode 100644
> index 000000000000..ff38302968c5
> --- /dev/null
> +++ b/Documentation/networking/device_drivers/ethernet/nebula-matrix/nbl.rst
> @@ -0,0 +1,28 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +================================================================
> +Linux Base Driver for Nebula-matrix m18110-NIC/m18000-NIC family
> +================================================================
> +
> +Overview:
> +=========
> +The m18110-NIC/m18000-NIC is a series of network interface cards for the Data
> +Center Area.
> +
> +The driver supports link-speed 100GbE/25GE/10GE.
> +
> +m18110-NIC/m18000-NIC devices support MSI-X interrupt vector for each Tx/Rx
> +queue and interrupt moderation.
> +
> +m18110-NIC/m18000-NIC devices support also various offload features such as
> +checksum offload, Receive-Side Scaling(RSS).
[Severity: Low]
Do these three statements describe what the driver actually does, either
at this commit or at the end of the series?
Grepping the vendor directory at the last patch of the series
("net/nebula-matrix: add common dev start/stop operation",
9b90629960395de83faaf5146e29ffc3cb854c5b) finds nothing for any of the
netdev or offload plumbing these sentences describe:
git grep -E 'register_netdev|netdev_ops|alloc_etherdev|ethtool_ops|NETIF_F_' \
drivers/net/ethernet/nebula-matrix/
(no matches)
The directory at that point contains only nbl_main.c plus nbl_channel/,
nbl_common/, nbl_core/, nbl_hw/ and nbl_include/, so the code binds the
PCI function, maps the BARs and brings up the PF mailbox, but never
registers a net_device, never programs per-queue Tx/Rx MSI-X vectors, and
has no RSS, checksum offload, interrupt moderation or link-speed
reporting.
Would it make sense to describe only what is implemented, and add the
link speed / per-queue MSI-X / moderation / RSS / checksum text in the
patches that introduce those features?
> +
> +Support
> +=======
> +
> +For more information about m18110-NIC/m18000-NIC, please visit the following URL:
> +https://www.nebula-matrix.com/snic_s1000_en
Is this the right product page? The URL names snic_s1000, while
nbl_main.c documents the matched IDs as "SNIC v3r1 product Device IDs
range: 0x3403-0x3412" for m18110/m18000.
> +
> +If an issue is identified with the released source code on the supported kernel
> +with a supported adapter, email the specific information related to the issue to
> +open@nebula-matrix.com.
[ ... ]
> diff --git a/drivers/net/ethernet/nebula-matrix/Kconfig b/drivers/net/ethernet/nebula-matrix/Kconfig
> new file mode 100644
> index 000000000000..f16e9663eaed
> --- /dev/null
> +++ b/drivers/net/ethernet/nebula-matrix/Kconfig
[ ... ]
> +config NBL
> + tristate "Nebula-matrix Ethernet Controller m18110/m18000 support"
> + depends on PCI && (64BIT || COMPILE_TEST) && !CPU_BIG_ENDIAN
> + help
> + This driver supports Nebula-matrix Ethernet Controller m18110/m18000
> + Family of devices.
> +
> + More specific information on configuring the driver is in
> + <file:Documentation/networking/device_drivers/ethernet/nebula-matrix/nbl.rst>.
The help text points users at the .rst above as the description of the
option's capabilities, so the same over-claim reaches anyone selecting
CONFIG_NBL: the prompt says "Ethernet Controller m18110/m18000 support",
but no network interface is created by any commit in this series.
[ ... ]
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260831021408.2325-1-illusion.wang%40nebula-matrix.com
next prev parent reply other threads:[~2026-09-03 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 2:13 [PATCH v26 net-next 00/10] nbl driver for Nebulamatrix NICs illusion.wang
2026-08-31 2:13 ` [PATCH v26 net-next 01/10] net/nebula-matrix: add minimum nbl build framework illusion.wang
2026-09-03 17:18 ` netdev-bot+sashiko [this message]
2026-08-31 2:13 ` [PATCH v26 net-next 02/10] net/nebula-matrix: add core driver architecture and HW layer initialization illusion.wang
2026-09-03 17:18 ` [v26,net-next,02/10] " netdev-bot+sashiko
2026-08-31 2:13 ` [PATCH v26 net-next 03/10] net/nebula-matrix: add channel layer illusion.wang
2026-09-03 17:18 ` [v26,net-next,03/10] " netdev-bot+sashiko
2026-08-31 2:13 ` [PATCH v26 net-next 04/10] net/nebula-matrix: add common resource implementation illusion.wang
2026-09-03 17:18 ` [v26,net-next,04/10] " netdev-bot+sashiko
2026-08-31 2:13 ` [PATCH v26 net-next 05/10] net/nebula-matrix: add intr " illusion.wang
2026-09-03 17:18 ` [v26,net-next,05/10] " netdev-bot+sashiko
2026-08-31 2:13 ` [PATCH v26 net-next 06/10] net/nebula-matrix: add chip-wide hardware init/deinit implementation illusion.wang
2026-09-03 17:18 ` [v26,net-next,06/10] " netdev-bot+sashiko
2026-08-31 2:13 ` [PATCH v26 net-next 07/10] net/nebula-matrix: dispatch: add control-level routing core infrastructure illusion.wang
2026-08-31 2:13 ` [PATCH v26 net-next 08/10] net/nebula-matrix: dispatch: implement channel RPC framework and serialize hardware ops illusion.wang
2026-09-03 17:18 ` [v26,net-next,08/10] " netdev-bot+sashiko
2026-08-31 2:14 ` [PATCH v26 net-next 09/10] net/nebula-matrix: add common/ctrl dev init/remove operation illusion.wang
2026-09-03 17:18 ` [v26,net-next,09/10] " netdev-bot+sashiko
2026-08-31 2:14 ` [PATCH v26 net-next 10/10] net/nebula-matrix: add common dev start/stop operation illusion.wang
2026-09-03 17:18 ` [v26,net-next,10/10] " netdev-bot+sashiko
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=178845591249.3394541.8367854604654150435@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=alvin.wang@nebula-matrix.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=dimon.zhao@nebula-matrix.com \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=illusion.wang@nebula-matrix.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sam.chen@nebula-matrix.com \
--cc=skhan@linuxfoundation.org \
--cc=vadim.fedorenko@linux.dev \
/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®