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 v19 net-next 00/11] nbl driver for Nebulamatrix NICs
Date: Wed, 17 Jun 2026 13:46:33 -0700 [thread overview]
Message-ID: <20260617134633.658a8c8e@kernel.org> (raw)
In-Reply-To: <20260617044702.2439-1-illusion.wang@nebula-matrix.com>
On Wed, 17 Jun 2026 12:46:45 +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.2,
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 June 29th.
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-06-17 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 4:46 [PATCH v19 net-next 00/11] nbl driver for Nebulamatrix NICs illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 01/11] net/nebula-matrix: add minimum nbl build framework illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 02/11] net/nebula-matrix: add our driver architecture illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 03/11] net/nebula-matrix: P4 configuration invoked during chip initialization illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 04/11] net/nebula-matrix: channel msg value and msg struct illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 05/11] net/nebula-matrix: add channel layer illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 06/11] net/nebula-matrix: add common resource implementation illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 07/11] net/nebula-matrix: add intr " illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 08/11] net/nebula-matrix: add vsi " illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 09/11] net/nebula-matrix: add Dispatch layer implementation illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 10/11] net/nebula-matrix: add common/ctrl dev init/remove operation illusion.wang
2026-06-17 4:46 ` [PATCH v19 net-next 11/11] net/nebula-matrix: add common dev start/stop operation illusion.wang
2026-06-17 20:46 ` 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=20260617134633.658a8c8e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.