linux-kernel - Re: [PATCH] spi: bcm2835aux: use 'unsigned int' instead of 'unsigned'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <162803013702.42391.3293196498865210081.b4-ty@kernel.org>
Date:   Tue,  3 Aug 2021 23:35:31 +0100
From:   Mark Brown <broonie@...nel.org>
To:     nsaenz@...nel.org, Jason Wang <wangborong@...rlc.com>
Cc:     Mark Brown <broonie@...nel.org>, rjui@...adcom.com,
        linux-rpi-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        bcm-kernel-feedback-list@...adcom.com, sbranden@...adcom.com,
        linux-arm-kernel@...ts.infradead.org, f.fainelli@...il.com,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: bcm2835aux: use 'unsigned int' instead of 'unsigned'

On Sat, 31 Jul 2021 21:33:42 +0800, Jason Wang wrote:
> 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