linux-kernel - Re: [PATCH -next v2 RESEND 0/2] spi: bcm63xx: Fix two bugs

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: <172415786506.39812.11128236652869415017.b4-ty@kernel.org>
Date: Tue, 20 Aug 2024 13:44:25 +0100
From: Mark Brown <broonie@...nel.org>
To: jonas.gorski@...il.com, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Jinjie Ruan <ruanjinjie@...wei.com>
Subject: Re: [PATCH -next v2 RESEND 0/2] spi: bcm63xx: Fix two bugs

On Mon, 19 Aug 2024 20:33:47 +0800, Jinjie Ruan wrote:
> Fix module autoloading and missing pm_runtime_disable().
> 
> Chanegs in v2:
> - Add Reviewed-by and Suggested-by.
> - Cc stable.
> - Change the fix way for the 2th patch.
> - Update the commit message.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: bcm63xx: Fix module autoloading
      commit: 909f34f2462a99bf876f64c5c61c653213e32fce
[2/2] spi: bcm63xx: Fix missing pm_runtime_disable()
      commit: 265697288ec2160ca84707565d6641d46f69b0ff

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