[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74306015-9e99-4703-b578-1d235dc725d5@suswa.mountain>
Date: Thu, 30 Nov 2023 10:07:08 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Nitesh Shetty <nj.shetty@...sung.com>
Cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
James Smart <james.smart@...adcom.com>,
Chaitanya Kulkarni <kch@...dia.com>, error27@...il.com,
gost.dev@...sung.com, nitheshshetty@...il.com,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] nvme: Update type from size_t to u16 for
opts->queue_size
On Wed, Nov 29, 2023 at 04:18:37PM +0530, Nitesh Shetty wrote:
> Thank you for this insight.
> I ran smatch on complete kernel using smatch's test_kernel.sh
> I was unaware of this smbd.py option. I will explore this.
The ./smatch_scripts/build_kernel_data.sh command creates the cross
function db. It takes a while though. And it's probably better to
run it a few times because every time you run it the call tree chains
get one call longer. I run it every night against the latest
linux-next.
> Meanwhile I feel this patch is still relevant, as it aligns opts
> queue_size with size of ctrl queue_size.
I don't have an opinion on this.
regards,
dan carpenter
Powered by blists - more mailing lists