[PATCH] spi: spidev_fdx: Fix the wrong format specifier

zhangjiao2 posted 1 patch 1 year, 5 months ago
tools/spi/spidev_fdx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] spi: spidev_fdx: Fix the wrong format specifier
Posted by zhangjiao2 1 year, 5 months ago
From: zhang jiao <zhangjiao2@cmss.chinamobile.com>

The unsigned int should use "%u" instead of "%d".

Signed-off-by: zhang jiao <zhangjiao2@cmss.chinamobile.com>
---
 tools/spi/spidev_fdx.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/spi/spidev_fdx.c b/tools/spi/spidev_fdx.c
index 7d2a867cd4ae..bc9c4f6c3ba8 100644
--- a/tools/spi/spidev_fdx.c
+++ b/tools/spi/spidev_fdx.c
@@ -99,7 +99,7 @@ static void dumpstat(const char *name, int fd)
 		return;
 	}
 
-	printf("%s: spi mode 0x%x, %d bits %sper word, %d Hz max\n",
+	printf("%s: spi mode 0x%x, %d bits %sper word, %u Hz max\n",
 		name, mode, bits, lsb ? "(lsb first) " : "", speed);
 }
 
-- 
2.33.0
Re: [PATCH] spi: spidev_fdx: Fix the wrong format specifier
Posted by Mark Brown 1 year, 5 months ago
On Wed, 04 Sep 2024 15:35:50 +0800, zhangjiao2 wrote:
> The unsigned int should use "%u" instead of "%d".
> 
> 

Applied to

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

Thanks!

[1/1] spi: spidev_fdx: Fix the wrong format specifier
      commit: dce35dd27684640508ff330b8235c4671159743e

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