linux-kernel - Re: [PATCHv2 0/3] add COMPILE

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: <175641485903.364382.15277195547103842587.b4-ty@kernel.org>
Date: Thu, 28 Aug 2025 23:00:59 +0200
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, Rosen Penev <rosenp@...il.com>
Cc: j4g8y7@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 0/3] add COMPILE_TEST support

On Tue, 26 Aug 2025 14:24:10 -0700, Rosen Penev wrote:
> Allows the buildbots to test compilation. The driver has nothing
> architecture specific.
> 
> v2: change to patch series and add extra patches
> 
> Rosen Penev (3):
>   spi: rb4xx: depend on OF
>   spi: rb4xx: add COMPILE_TEST support
>   spi: rb4xx: use devm for clk_prepare_enable
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: rb4xx: depend on OF
      commit: c73c378dc05ba8060558b9b50e37f3afa4763ea1
[2/3] spi: rb4xx: add COMPILE_TEST support
      commit: f18f0ac5331f8f13737e87cc1416837fb5b27b0a
[3/3] spi: rb4xx: use devm for clk_prepare_enable
      commit: ff9a7857b7848227788f113d6dc6a72e989084e0

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