[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241009110842.jhtyt6ckbfp6medf@skbuf>
Date: Wed, 9 Oct 2024 14:08:42 +0300
From: Vladimir Oltean <olteanv@...il.com>
To: Hardevsinh Palaniya <hardevsinh.palaniya@...iconsignals.io>
Cc: Marc Kleine-Budde <mkl@...gutronix.de>,
"broonie@...nel.org" <broonie@...nel.org>,
"frank.li@....com" <frank.li@....com>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"imx@...ts.linux.dev" <imx@...ts.linux.dev>,
Sascha Hauer <s.hauer@...gutronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>
Subject: Re: Fix Sparse warnings
On Tue, Oct 08, 2024 at 08:43:51AM +0000, Hardevsinh Palaniya wrote:
> >Have you checked the code on real hardware or compared the generated
> >code on the asm level?
>
> it's just resolve casting warnings so....
>
> No, I haven’t tested the code on real hardware.
>
> Are there alternative methods to verify it without using hardware?
"Comparing the generated code on the asm level" means running
"make drivers/spi/spi-imx.lst" before and after the patch, FWIW.
It's about the most you can do in absence of hardware to test on.
Powered by blists - more mailing lists