linux-kernel - Re: [PATCH] ASoC: cs35l56: Log a message if firmware is missing

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: <176436571350.232510.7650120666844121045.b4-ty@kernel.org>
Date: Fri, 28 Nov 2025 21:35:13 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Log a message if firmware is missing

On Fri, 28 Nov 2025 11:25:20 +0000, Richard Fitzgerald wrote:
> If the amp is still reporting FIRMWARE_MISSING after cs35l56_patch()
> has completed it is helpful to log a warning.
> 
> After a complete firmware download the FIRMWARE_MISSING flag will be
> clear. If this isn't the case, the driver should log a message to
> report this.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Log a message if firmware is missing
      commit: 816c9cac35185aff33da1eb73cc974349623eb3a

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