linux-kernel - Re: [PATCH 1/2] ASoC: codecs: aw88395: Simplify with cleanup.h

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: <172063262990.22653.3673550348945714885.b4-ty@kernel.org>
Date: Wed, 10 Jul 2024 18:30:29 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, 
 Banajit Goswami <bgoswami@...cinc.com>, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, alsa-devel@...a-project.org, 
 linux-arm-msm@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH 1/2] ASoC: codecs: aw88395: Simplify with cleanup.h

On Mon, 01 Jul 2024 19:19:16 +0200, Krzysztof Kozlowski wrote:
> Allocate memory, which is being freed at end of the scope, with
> scoped/cleanup.h to reduce number of error paths and make code a bit
> simpler.
> 
> 

Applied to

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

Thanks!

[1/2] ASoC: codecs: aw88395: Simplify with cleanup.h
      commit: d0f4ce8a28dd992579949b8ea2df810c4b5fe9b5
[2/2] ASoC: qcom: topology: Simplify with cleanup.h
      commit: a8915e2fe86c29304a3038f269f4667b371b87d2

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