spi: bcm2835aux: use 'unsigned int' instead of 'unsigned'
Subsystems (3)
PATCH 1/1 spi: bcm2835aux: use 'unsigned int' instead of 'unsigned'
Prefer 'unsigned int' to bare use of 'unsigned'.
--- drivers/spi/spi-bcm2835aux.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/spi/spi-bcm2835aux.c +2 -2
@@ -143,12 +143,12 @@ static void bcm2835aux_debugfs_remove(struct bcm2835aux_spi *bs) }#endif /* CONFIG_DEBUG_FS */ -static inline u32 bcm2835aux_rd (struct bcm2835aux_spi *bs,unsigned reg) +static inline u32 bcm2835aux_rd (struct bcm2835aux_spi *bs,unsigned int reg) {return readl (bs->regs + reg); } -static inline void bcm2835aux_wr (struct bcm2835aux_spi *bs,unsigned reg, +static inline void bcm2835aux_wr (struct bcm2835aux_spi *bs,unsigned int reg,u32 val) {writel (val, bs->regs + reg);
Signature · 1 line
2.32.0
Mark Brown
maintainerQuoted 1 line · Jason Wang
Prefer 'unsigned int' to bare use of 'unsigned'.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: bcm2835aux: use 'unsigned int' instead of 'unsigned'
commit: b09bff2676be3ae286e6161a1a581a40c53a3c62
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