Skip to contentSkip to conversation

spi: sophgo: fix incorrect type for ret in sg2044_spifmc_write()

PATCH In review Qasim Ijaz 2 participants 2 messages Mar 13, 2025 – Mar 17, 2025 SPI

lore
Share & tools
lore

Qasim Ijaz

author
#0 lore raw

PATCH 1/1 spi: sophgo: fix incorrect type for ret in sg2044_spifmc_write()

The sg2044_spifmc_write() function uses 'ret' of unsigned type size_t to capture return values from sg2044_spifmc_wait_xfer_size() and sg2044_spifmc_wait_int(). Since these functions may return negative error codes, using an unsigned type prevents proper error detection, as size_t cannot represent negative values.

Change 'ret' to type int so that negative values are handled correctly.

Fixes de16c322eefb ("spi: sophgo: add SG2044 SPI NOR controller driver")
---
 drivers/spi/spi-sg2044-nor.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi-sg2044-nor.c +1 -1
index 454153a63b42..baa4cf677663 100644
@@ -216,7 +216,7 @@ static ssize_t sg2044_spifmc_write(struct sg2044_spifmc *spifmc,
 	size_t xfer_size;
 	const u8 *dout = op->data.buf.out;
 	int i, offset;
-	size_t ret;
+	int ret;
 	u32 reg;
 
 	reg = sg2044_spifmc_init_reg(spifmc);
Signature · 1 line
2.39.5
maintainer
#1 lore raw
Quoted 9 lines · Qasim Ijaz

The sg2044_spifmc_write() function uses 'ret' of unsigned type size_t to capture return values from sg2044_spifmc_wait_xfer_size() and sg2044_spifmc_wait_int(). Since these functions may return negative error codes, using an unsigned type prevents proper error detection, as size_t cannot represent negative values.

Change 'ret' to type int so that negative values are handled correctly.

[...]

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: sophgo: fix incorrect type for ret in sg2044_spifmc_write()

      commit: 3c9403f150b70d76198e414d53c95e1698e3f99f

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark