linux-kernel - Re: [PATCH] ASoC: cs35l41: check the return value from spi

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: <174169911354.27942.6320813345687980941.b4-ty@kernel.org>
Date: Tue, 11 Mar 2025 13:18:33 +0000
From: Mark Brown <broonie@...nel.org>
To: David Rhodes <david.rhodes@...rus.com>, 
 Vitaliy Shevtsov <v.shevtsov@...integration.ru>
Cc: Richard Fitzgerald <rf@...nsource.cirrus.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Lucas Tanure <tanureal@...nsource.cirrus.com>, 
 Charles Keepax <ckeepax@...nsource.cirrus.com>, linux-sound@...r.kernel.org, 
 patches@...nsource.cirrus.com, linux-kernel@...r.kernel.org, 
 lvc-project@...uxtesting.org
Subject: Re: [PATCH] ASoC: cs35l41: check the return value from spi_setup()

On Tue, 04 Mar 2025 16:56:37 +0500, Vitaliy Shevtsov wrote:
> Currently the return value from spi_setup() is not checked for a failure.
> It is unlikely it will ever fail in this particular case but it is still
> better to add this check for the sake of completeness and correctness. This
> is cheap since it is performed once when the device is being probed.
> 
> Handle spi_setup() return value.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l41: check the return value from spi_setup()
      commit: ad5a0970f86d82e39ebd06d45a1f7aa48a1316f8

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