linux-kernel - Re: [PATCH] sound: soc: stm: stm32_sai: Use dev_err

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: <174406894704.1337819.6120750262182718363.b4-ty@kernel.org>
Date: Tue, 08 Apr 2025 00:35:47 +0100
From: Mark Brown <broonie@...nel.org>
To: olivier.moysan@...s.st.com, shao.mingyin@....com.cn
Cc: arnaud.pouliquen@...s.st.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, mcoquelin.stm32@...il.com, alexandre.torgue@...s.st.com, 
 linux-sound@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 yang.yang29@....com.cn, xu.xin16@....com.cn, ye.xingchen@....com.cn, 
 zhang.enpei@....com.cn
Subject: Re: [PATCH] sound: soc: stm: stm32_sai: Use dev_err_probe()

On Thu, 03 Apr 2025 15:41:42 +0800, shao.mingyin@....com.cn wrote:
> Replace the open-code with dev_err_probe() to simplify the code.
> 
> 

Applied to

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

Thanks!

[1/1] sound: soc: stm: stm32_sai: Use dev_err_probe()
      commit: d01131e3ce14f9837884aef1f3e463a3a492291f

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