linux-kernel - Re: [PATCH] ASoC: cs35l56: probe() should fail if the device ID is not recognized

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: <175156262505.651944.17565796776876506134.b4-ty@kernel.org>
Date: Thu, 03 Jul 2025 18:10:25 +0100
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: probe() should fail if the device ID is
 not recognized

On Thu, 03 Jul 2025 11:25:21 +0100, Richard Fitzgerald wrote:
> Return an error from driver probe if the DEVID read from the chip is not
> one supported by this driver.
> 
> In cs35l56_hw_init() there is a check for valid DEVID, but the invalid
> case was returning the value of ret. At this point in the code ret == 0
> so the caller would think that cs35l56_hw_init() was successful.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: probe() should fail if the device ID is not recognized
      commit: 3b3312f28ee2d9c386602f8521e419cfc69f4823

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