The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Illusion Wang <Illusion.Wang@nebula-matrix.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
	Dimon <dimon.zhao@nebula-matrix.com>,
	Alvin <alvin.wang@nebula-matrix.com>,
	Sam <sam.chen@nebula-matrix.com>, netdev <netdev@vger.kernel.org>,
	andrew+netdev <andrew+netdev@lunn.ch>, corbet <corbet@lwn.net>,
	kuba <kuba@kernel.org>, linux-doc <linux-doc@vger.kernel.org>,
	lorenzo <lorenzo@kernel.org>, horms <horms@kernel.org>,
	"vadim.fedorenko" <vadim.fedorenko@linux.dev>,
	"lukas.bulwahn" <lukas.bulwahn@redhat.com>,
	edumazet <edumazet@google.com>,
	enelsonmoore <enelsonmoore@gmail.com>,
	skhan <skhan@linuxfoundation.org>,
	hkallweit1 <hkallweit1@gmail.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: 回复:回复:[PATCH v13 net-next 03/11] net/nebula-matrix: add chip related definitions
Date: Sat, 9 May 2026 21:43:18 +0200	[thread overview]
Message-ID: <ba0d1a60-3d56-4053-a4e9-e47fda0c450a@lunn.ch> (raw)
In-Reply-To: <e35c8cf4-73f0-4847-b1b1-8f424a805a71.Illusion.Wang@nebula-matrix.com>

On Sat, May 09, 2026 at 11:38:27AM +0800, Illusion Wang wrote:
> 
> >> But I printed out the results: 
> >> ARRAY_SIZE(nbl_sec009_data) equals NBL_SEC009_SIZE,
> >> ARRAY_SIZE(nbl_sec025_data) equals NBL_SEC025_SIZE,
> >> and ARRAY_SIZE(nbl_sec022_data) equals NBL_SEC022_SIZE.
> >> 
> >> Is the AI making a mistake here?
> 
> >Just a guess, i've not looked at this patch at all.
> 
> >Are you doing this on a 32 bit build? Maybe the AI is?
> 
>  >   Andrew
> 
>  We are using this on a 64 bit build.

And what happens with a 32 bit build? Try think of all the ways the AI
could be correct., and disprove them.

      Andrew

  reply	other threads:[~2026-05-09 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260428114910.2616-1-illusion.wang@nebula-matrix.com>
     [not found] ` <20260428114910.2616-4-illusion.wang@nebula-matrix.com>
     [not found]   ` <e41adaad-8937-4b5d-bdbf-d57d3efe2855@redhat.com>
2026-05-08  4:52     ` 回复:[PATCH v13 net-next 03/11] net/nebula-matrix: add chip related definitions Illusion Wang
2026-05-08 13:40       ` Andrew Lunn
2026-05-09  3:38         ` 回复:回复:[PATCH " Illusion Wang
2026-05-09 19:43           ` Andrew Lunn [this message]
     [not found] ` <20260428114910.2616-6-illusion.wang@nebula-matrix.com>
     [not found]   ` <d8f24185-9987-487a-9e0c-5387bd72b629@redhat.com>
2026-05-09  3:46     ` 回复:[PATCH v13 net-next 05/11] net/nebula-matrix: add channel layer Illusion Wang

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=ba0d1a60-3d56-4053-a4e9-e47fda0c450a@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Illusion.Wang@nebula-matrix.com \
    --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=kuba@kernel.org \
    --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=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