From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Hardevsinh Palaniya <hardevsinh.palaniya@siliconsignals.io>
Cc: olteanv@gmail.com, broonie@kernel.org, frank.li@nxp.com,
shawnguo@kernel.org, imx@lists.linux.dev,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: Fix Sparse warnings
Date: Tue, 8 Oct 2024 08:25:52 +0200 [thread overview]
Message-ID: <20241008-impossible-mysterious-salmon-e1b8bd-mkl@pengutronix.de> (raw)
In-Reply-To: <20241008055644.4900-1-hardevsinh.palaniya@siliconsignals.io>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
On 08.10.2024 11:25:44, Hardevsinh Palaniya wrote:
> Change in v2:
>
> 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?
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-10-08 6:28 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 ` Marc Kleine-Budde [this message]
2024-10-08 8:43 ` Fix Sparse warnings Hardevsinh Palaniya
2024-10-09 11:08 ` Vladimir Oltean
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=20241008-impossible-mysterious-salmon-e1b8bd-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--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=olteanv@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).