public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
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, linux-doc@vger.kernel.org,
	lorenzo@kernel.org, pabeni@redhat.com, horms@kernel.org,
	vadim.fedorenko@linux.dev, lukas.bulwahn@redhat.com,
	edumazet@google.com, linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH v2 net-next 00/15] nbl driver for Nebulamatrix NICs
Date: Fri, 9 Jan 2026 16:20:51 -0800	[thread overview]
Message-ID: <20260109162051.42f71451@kernel.org> (raw)
In-Reply-To: <20260109100146.63569-1-illusion.wang@nebula-matrix.com>

On Fri,  9 Jan 2026 18:01:18 +0800 illusion.wang wrote:
>  61 files changed, 43278 insertions(+)

No way anyone can review 45kLoC.
Please cut this down to a minimal driver - ~5kLoC + patch 4.

      parent reply	other threads:[~2026-01-10  0:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 10:01 [PATCH v2 net-next 00/15] nbl driver for Nebulamatrix NICs illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 01/15] net/nebula-matrix: add minimum nbl build framework illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 02/15] net/nebula-matrix: add simple probe/remove illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 03/15] net/nebula-matrix: add HW layer definitions and implementation illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 04/15] net/nebula-matrix: add machine-generated headers and chip definitions illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 05/15] net/nebula-matrix: add channel layer definitions and implementation illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 06/15] net/nebula-matrix: add resource " illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 07/15] net/nebula-matrix: add intr resource " illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 08/15] net/nebula-matrix: add vsi, queue, adminq " illusion.wang
2026-01-09 18:38   ` Andrew Lunn
2026-01-09 10:01 ` [PATCH v2 net-next 09/15] net/nebula-matrix: add flow " illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 10/15] net/nebula-matrix: add txrx " illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 11/15] net/nebula-matrix: add Dispatch layer " illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 12/15] net/nebula-matrix: add Service " illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 13/15] net/nebula-matrix: add Dev init,remove operation illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 14/15] net/nebula-matrix: add Dev start, stop operation illusion.wang
2026-01-09 10:01 ` [PATCH v2 net-next 15/15] net/nebula-matrix: add st_sysfs and vf name sysfs illusion.wang
2026-01-09 18:40   ` Andrew Lunn
2026-01-10  0:20 ` 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=20260109162051.42f71451@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=horms@kernel.org \
    --cc=illusion.wang@nebula-matrix.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sam.chen@nebula-matrix.com \
    --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