[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PN0P287MB2843E06597DD5D64BE93A8A7FF7E2@PN0P287MB2843.INDP287.PROD.OUTLOOK.COM>
Date: Tue, 8 Oct 2024 08:43:51 +0000
From: Hardevsinh Palaniya <hardevsinh.palaniya@...iconsignals.io>
To: Marc Kleine-Budde <mkl@...gutronix.de>
CC: "olteanv@...il.com" <olteanv@...il.com>, "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
Hi Marc,
>> in patch 2/2:
>> - Use ioread32be instead of readl
>> - Use iowrite32be instead of writel
>>
>> Note: Drop 2 patches(patch 2/4 & 4/4) from the last version
>> link to v1: https://lore.kernel.org/linux-spi/20240927132944.19285-1-hardevsinh.palaniya@siliconsignals.io/T/#t
>
>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?
Best Regards,
Hardev
Powered by blists - more mailing lists