linux-kernel - Re: [PATCH] ASoC: max98088: Check for clk_prepare

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <171959441401.130075.12388433087390815792.b4-ty@kernel.org>
Date: Fri, 28 Jun 2024 18:06:54 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 m.felsch@...gutronix.de, trblinux@...il.com, javier@....samsung.com, 
 afaerber@...e.de, Chen Ni <nichen@...as.ac.cn>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: max98088: Check for clk_prepare_enable() error

On Fri, 28 Jun 2024 16:05:34 +0800, Chen Ni wrote:
> clk_prepare_enable() may fail, so we should better check its return
> value and propagate it in the case of error.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: max98088: Check for clk_prepare_enable() error
      commit: 1a70579723fde3624a72dfea6e79e55be6e36659

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