From: Jakub Kicinski <kuba@kernel.org>
To: "illusion.wang" <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, 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 (open list)
Subject: Re: [PATCH v25 net-next 00/10] nbl driver for Nebulamatrix NICs
Date: Tue, 18 Aug 2026 17:28:15 -0700 [thread overview]
Message-ID: <20260818172815.5f2fc6b1@kernel.org> (raw)
In-Reply-To: <20260819001117.46785-1-illusion.wang@nebula-matrix.com>
On Wed, 19 Aug 2026 08:11:02 +0800 illusion.wang wrote:
> This patch series represents the first phase. We plan to integrate it in
> two phases: the first phase covers mailbox and chip configuration,
> while the second phase involves net dev configuration.
> Together, they will provide basic PF-based Ethernet port transmission and
> reception capabilities.
## Form letter - net-next-closed
We have already submitted our pull request with net-next material for v7.3,
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 Aug 31st.
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
prev parent reply other threads:[~2026-08-19 0:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 0:11 [PATCH v25 net-next 00/10] nbl driver for Nebulamatrix NICs illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 01/10] net/nebula-matrix: add minimum nbl build framework illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 02/10] net/nebula-matrix: add core driver architecture and HW layer initialization illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 03/10] net/nebula-matrix: add channel layer illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 04/10] net/nebula-matrix: add common resource implementation illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 05/10] net/nebula-matrix: add intr " illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 06/10] net/nebula-matrix: add chip-wide hardware init/deinit implementation illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 07/10] net/nebula-matrix: dispatch: add control-level routing core infrastructure illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 08/10] net/nebula-matrix: dispatch: implement channel RPC framework and serialize hardware ops illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 09/10] net/nebula-matrix: add common/ctrl dev init/remove operation illusion.wang
2026-08-19 0:11 ` [PATCH v25 net-next 10/10] net/nebula-matrix: add common dev start/stop operation illusion.wang
2026-08-19 0:28 ` 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=20260818172815.5f2fc6b1@kernel.org \
--to=kuba@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=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