From: Vladimir Oltean <olteanv@gmail.com>
To: Hardevsinh Palaniya <hardevsinh.palaniya@siliconsignals.io>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
"broonie@kernel.org" <broonie@kernel.org>,
"frank.li@nxp.com" <frank.li@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
Sascha Hauer <s.hauer@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: Fix Sparse warnings
Date: Wed, 9 Oct 2024 14:08:42 +0300 [thread overview]
Message-ID: <20241009110842.jhtyt6ckbfp6medf@skbuf> (raw)
In-Reply-To: <PN0P287MB2843E06597DD5D64BE93A8A7FF7E2@PN0P287MB2843.INDP287.PROD.OUTLOOK.COM>
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.
next prev parent reply other threads:[~2024-10-09 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 5:55 Fix Sparse warnings Hardevsinh Palaniya
2024-10-08 5:55 ` [PATCH v2 1/2] spi: spi-fsl-dspi: Fix casting warnings Hardevsinh Palaniya
2024-10-08 13:13 ` Vladimir Oltean
2024-10-08 5:55 ` [PATCH v2 2/2] spi: spi-imx: " Hardevsinh Palaniya
2024-10-08 15:29 ` Frank Li
2024-10-08 6:25 ` Fix Sparse warnings Marc Kleine-Budde
2024-10-08 8:43 ` Hardevsinh Palaniya
2024-10-09 11:08 ` Vladimir Oltean [this message]
2024-10-10 11:14 ` Mark Brown
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=20241009110842.jhtyt6ckbfp6medf@skbuf \
--to=olteanv@gmail.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=hardevsinh.palaniya@siliconsignals.io \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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