From: Paolo Abeni <pabeni@redhat.com>
To: "illusion.wang" <illusion.wang@nebula-matrix.com>,
dimon.zhao@nebula-matrix.com, alvin.wang@nebula-matrix.com,
sam.chen@nebula-matrix.com, netdev@vger.kernel.org
Cc: open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 net-next 00/15] nbl driver for Nebulamatrix NICs
Date: Tue, 23 Dec 2025 08:08:30 +0100 [thread overview]
Message-ID: <a9e7c86b-1a08-4ea4-bf41-75d406a13923@redhat.com> (raw)
In-Reply-To: <20251223035113.31122-1-illusion.wang@nebula-matrix.com>
On 12/23/25 4:50 AM, illusion.wang wrote:
> The patch series add the nbl driver, which will support the nebula-matrix 18100 and 18110 series
> of network cards.
> This submission is the first phase. which includes the PF-based and VF-based Ethernet transmit
> and receive functionality. Once this is merged. will submit addition patches to implement support
> for other features. such as ethtool support, debugfs support and etc.
> Our Driver architecture supports Kernel Mode and Coexistence Mode(kernel and dpdk)
Not a real review, but this series has several basic issues:
- each patch should compile and build without warnings on all arches
- don't use inline in c code
- avoid using 'module_params'
- the preferred line width is still 80 chars
- strip changed-id from the commit message
- respect the reverse christmas tree order for variable declaration
- commit messages lines should be wrapped at 72 chars
Note that you can clone the NIPA repository:
https://github.com/linux-netdev/nipa/
and use the ingest_mdir.py script to validate most of the above check
before submission (otherwise you should do that manually).
However...
## Form letter - net-next-closed
The net-next tree is closed for new drivers, features, code refactoring
and optimizations due to the merge window and the winter break. We are
currently accepting bug fixes only.
Please repost when net-next reopens after Jan 2nd.
RFC patches sent for review only are obviously welcome at any time.
next prev parent reply other threads:[~2025-12-23 7:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 3:50 illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 01/15] net/nebula-matrix: add minimum nbl build framework illusion.wang
2025-12-23 10:02 ` Andrew Lunn
2025-12-23 3:50 ` [PATCH v1 net-next 02/15] net/nebula-matrix: add simple probe/remove illusion.wang
2025-12-23 10:19 ` Andrew Lunn
2025-12-23 3:50 ` [PATCH v1 net-next 03/15] net/nebula-matrix: add HW layer definitions and implementation illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 04/15] net/nebula-matrix: add Channel " illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 05/15] net/nebula-matrix: add Resource " illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 06/15] net/nebula-matrix: add intr resource " illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 07/15] net/nebula-matrix: add vsi, queue, adminq " illusion.wang
2025-12-24 10:49 ` Andrew Lunn
2025-12-23 3:50 ` [PATCH v1 net-next 08/15] net/nebula-matrix: add flow " illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 09/15] net/nebula-matrix: add txrx " illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 10/15] net/nebula-matrix: add Dispatch layer " illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 11/15] net/nebula-matrix: add Service " illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 12/15] net/nebula-matrix: add Dev " illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 13/15] net/nebula-matrix: add Dev start, stop operation illusion.wang
2025-12-24 11:03 ` Andrew Lunn
2025-12-29 1:36 ` 回复:[PATCH " Illusion Wang
2025-12-23 3:50 ` [PATCH v1 net-next 14/15] net/nebula-matrix: fully support ndo operations illusion.wang
2025-12-23 3:50 ` [PATCH v1 net-next 15/15] net/nebula-matrix: add kernel/user coexist mode support illusion.wang
2025-12-24 10:52 ` Andrew Lunn
2025-12-23 7:08 ` Paolo Abeni [this message]
2025-12-29 1:47 ` 回复:[PATCH v1 net-next 00/15] nbl driver for Nebulamatrix NICs Illusion Wang
2025-12-29 16:41 ` Paolo Abeni
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=a9e7c86b-1a08-4ea4-bf41-75d406a13923@redhat.com \
--to=pabeni@redhat.com \
--cc=alvin.wang@nebula-matrix.com \
--cc=dimon.zhao@nebula-matrix.com \
--cc=illusion.wang@nebula-matrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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®