[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aXnT1juyBbMkiykg@horms.kernel.org>
Date: Wed, 28 Jan 2026 09:16:06 +0000
From: Simon Horman <horms@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "illusion.wang" <illusion.wang@...ula-matrix.com>,
dimon.zhao@...ula-matrix.com, alvin.wang@...ula-matrix.com,
sam.chen@...ula-matrix.com, netdev@...r.kernel.org,
andrew+netdev@...n.ch, corbet@....net, linux-doc@...r.kernel.org,
lorenzo@...nel.org, pabeni@...hat.com, vadim.fedorenko@...ux.dev,
lukas.bulwahn@...hat.com, hawk@...nel.org, ast@...nel.org,
bpf@...r.kernel.org, sdf@...ichev.me, daniel@...earbox.net,
john.fastabend@...il.com, edumazet@...gle.com,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 net-next 00/15] nbl driver for Nebulamatrix NICs
On Tue, Jan 27, 2026 at 10:53:04AM -0800, Jakub Kicinski wrote:
> On Tue, 27 Jan 2026 18:06:49 +0000 Simon Horman wrote:
> > As per Jakub's advice in his review of v1 [*],
> > Please try to create a minimal driver in the order of ~5kLoC.
>
> Perhaps other maintainers will disagree, but for ease of review
> and to avoid the huge reposts perhaps we should consider merging
> something like patches 1 and 3* first, as the initial series.
> And then you can build up the driver from there in reasonable,
> 5kLoC-at-a-time series?
>
> * patch 3 currently includes things which do not seem machine
> generated / like register descriptors like structs added to
> nbl_def_channel.h and nbl_include.h
Without having looked into the details: yes, I think some
sort of staged approached could help here.
Powered by blists - more mailing lists