linux-kernel - Re: [PATCH 0/2] spi: Remove redundant semicolons

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 for Android: free password hash cracker in your pocket

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

Message-Id: <175500549067.70594.14172853876781002627.b4-ty@kernel.org>
Date: Tue, 12 Aug 2025 14:31:30 +0100
From: Mark Brown <broonie@...nel.org>
To: Florian Fainelli <florian.fainelli@...adcom.com>, 
 Ray Jui <rjui@...adcom.com>, Scott Branden <sbranden@...adcom.com>, 
 Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>, 
 Matthias Brugger <matthias.bgg@...il.com>, 
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, 
 Martin Sperl <kernel@...tin.sperl.org>, Chuanhong Guo <gch981213@...il.com>, 
 linux-spi@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 linux-mediatek@...ts.infradead.org, Liao Yuanhong <liaoyuanhong@...o.com>
Subject: Re: [PATCH 0/2] spi: Remove redundant semicolons

On Tue, 12 Aug 2025 11:38:15 +0800, Liao Yuanhong wrote:
> Clean up the code by removing redundant semicolons.
> 
> Liao Yuanhong (2):
>   spi: bcm2835: Remove redundant semicolons
>   spi: mtk-snfi: Remove redundant semicolons
> 
> drivers/spi/spi-bcm2835.c  | 2 +-
>  drivers/spi/spi-mtk-snfi.c | 1 -
>  2 files changed, 1 insertion(+), 2 deletions(-)
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: bcm2835: Remove redundant semicolons
      commit: 0ecc0e17f05bbb953b6ea3812e78bab224f08595
[2/2] spi: mtk-snfi: Remove redundant semicolons
      commit: 528a813a5d98702cc6fd51983484cf7eec9ebcac

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